agentleFS
manhds82manhds82/claude-code-anyllm/.claude/skills/verify-implementation/SKILL.md

verify-implementation

Skill16 starsChanged 37 days agoMITView on GitHub

Verify an implementation against its acceptance criteria and the judge rubric, run tests, and emit an APPROVED/CHANGES_REQUIRED/REJECTED verdict — the verification stage (H3).

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

verify-implementation

The verification node of the DAG (review profile). Feeds the hard-gate (hard-gate.ps1): APPROVED continues, CHANGES_REQUIRED loops back to implementation (retry counter), REJECTED halts for human intervention (H3/H5).

Pairs reviewer (judges) with tester (actually runs suites) so the verdict rests on executed tests, not on reading the diff alone.

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.