agentleFS
Sign inStart free
KbWenKbWen/agentic-os/.agents/skills/verification-before-completion/SKILL.md

verification-before-completion

Skill224 starsChanged 20 days agoMITView on GitHub

Enforce "no evidence = no completion"; run Gate Function verification before declaring done.

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If tests/checks fail, the status MUST revert to in-progress.

    line 16
  2. Distinctive:

    Before submitting PRs or handing off work.

    line 21
  3. Distinctive:

    After completing high-risk changes (data, permissions, core flows).

    line 22
  4. Distinctive:

    If there are unfinished items, explicitly mark them with follow-up suggestions.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Verification Before Completion

Overview

Any "completed" statement MUST be supported by evidence. This skill provides a pre-completion Gate Function, ensuring results are reproducible, traceable, and deliverable.

Ironclad Rules

  • No evidence = no completion claim.
  • Evidence MUST be reproducible by others; verbal descriptions are NOT accepted.
  • If tests/checks fail, the status MUST revert to in-progress.

When to Use

  • Tasks are preparing to enter /ship.
  • Before submitting PRs or handing off work.
  • After completing high-risk changes (data, permissions, core flows).

Gate Function

  1. Scope Gate: Confirm changes only cover the agreed scope.
  2. Quality Gate: Execute required tests and static checks.
  3. Evidence Gate: Compile reproducible evidence (commands, outputs, versions).
  4. Risk Gate: Confirm rollback strategies and known risks.
  5. Communication Gate: Output a completion summary (changes, validation, constraints).

Minimum Evidence Checklist

  • At least one set of tests/checks directly related to this change.
  • Specific execution commands and results (Success/Failure/Warning).
  • If there are unfinished items, explicitly mark them with follow-up suggestions.

Common Mistakes

  • Claiming "it should work" without any output evidence.
  • Testing only the happy path, missing regressions or edge cases.
  • Treating old test results as evidence for new changes.

Download now (ZIP)

  • Other versions187 projects use a version of this.

    Word for word · 1

    1. KbWen/agent-virtual-office★ 65100% same

    Edited · 0

    None found.

    Wrote their own version · 186

    1. obra/superpowers★ 305ksame name
    2. jnMetaCode/superpowers-zh★ 8.4ksame name
    3. openai/plugins★ 7.4ksame name
    4. farm-fe/farm★ 5.6ksame name
    5. GanyuanRan/Aegis★ 1.4ksame name
    6. pcvelz/superpowers★ 1.3ksame name
    7. coco-research/coco★ 797same name
    8. pedronauck/skills★ 641same name
    9. koaning/wigglystuff★ 455same name
    10. derHaken/SuperAntigravity★ 439same name

    176 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • GEd520Skill

      chinese-code-review

      中文 review 沟通参考——话术模板、分级标注（必须修复/建议修改/仅供参考）、国内团队常见反模式应对。仅在用户显式 /chinese-code-review 时调用，不要根据上下文自动触发。

      Also in 7 projects that use this

    • GEd520Skill

      chinese-commit-conventions

      中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。

      Also in 7 projects that use this

    • obraSkill

      diagnosing-superpowers

      Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

      Also in 12 projects that use this

    • 10CGSkill

      workflow-runner

      十步循环轻量编排器，协调 Phase Skills 执行，支持灵活组合。

      Also in 7 projects that use this

    • MicrosoftSkill

      root-cause-tracing

      Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

      Also in 6 projects that use this

    • kntismSkill

      condition-based-waiting

      Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

      Also in 3 projects that use this

    • +2 more from GEd520
  • In this repository17 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free