agentleFS
jsuvicjsuvic/agent-profile/.claude/skills/final-review/SKILL.md

final-review

Skill3 starsChanged 3 months agoApache-2.0View on GitHub

Use before handing off an implementation to compare the diff against the spec, tests, docs, contracts, and safety rules.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 2

    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:

    Check generated outputs for deterministic formatting and intentional fixture changes.

    line 15
  2. Distinctive:

    Check that no literal secrets, production access, unsafe auto-approval, source upload, or automatic dependency installation were introduced.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 7 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
<!-- Generated by Agent Profile Compiler. Do not edit by hand. -->

Final Review

Instructions

  1. Compare the implementation against the relevant spec.
  2. Confirm acceptance criteria are met or list the unmet criteria.
  3. Confirm tests and golden tests were run when applicable.
  4. Check generated outputs for deterministic formatting and intentional fixture changes.
  5. Check that no literal secrets, production access, unsafe auto-approval, source upload, or automatic dependency installation were introduced.
  6. Report remaining risks, TODOs, and documentation gaps. When change-risk review applies, validate the closed snapshot-bound ChangeRiskOrchestrationStateV1 handoff from subagent-driven-change; accept a terminal result only when its snapshot matches the final snapshot modulo docs/review-learning/, and do not run another review or interpret prose state.

Output

Return a concise final review with spec compliance, tests run, contract impact, security impact, and remaining risks.

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.