final-review
Skill38 starsChanged 2 months agoMITView on GitHub
Final Review
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Tire-C/final-review-skilltheir own version, first seen Nov 16, 2026
- normalled/apijacktheir own version, first seen Nov 8, 2026
- MrD-Lt/codex-final-reviewtheir own version, first seen Nov 7, 2026
- DanMcInerney/architect-looptheir own version, first seen Oct 8, 2026
- andeeplus/aplustheir own version, first seen Oct 4, 2026
- jsuvic/agent-profiletheir own version, first seen Aug 5, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- DanMcInerney/architect-loop★ 626same name
- aromanarguello/roman-skills★ 18same name
- normalled/apijack★ 7same name
- limpidwei/final-exam-review★ 5same name
- jsuvic/agent-profile★ 3same name
- andeeplus/aplus★ 2same name
- MrD-Lt/codex-final-review★ 2same name
- Tire-C/final-review-skill★ 2same name
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.
In this repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/autonomous_execution.mdcCursor rule
- .cursor/rules/cursor_rules_editing.mdcCursor rule
- .cursor/rules/cursor_rules_sync.mdcCursor rule
- .cursor/rules/cursor_rules_sync_requirement.mdcCursor rule
- site_pages/llms.txtllms.txt
- advisorySkill
- analyzeSkill
- auditSkill
- commitSkill
- create-planSkill
- create_planSkill
- create-prototypeSkill
- create_prototypeSkill
- create_prSkill
- create-releaseSkill
- create_releaseSkill
- create-ruleSkill
- create_ruleSkill
- debugSkill
- draft-illustrationSkill
- draft_illustrationSkill
- endSkill
- evaluate_positioningSkill
- final_reviewSkill
- fix-feature-bugSkill
- fix_feature_bugSkill
- learnSkill
- manage-error-debuggingSkill
- manage_error_debuggingSkill
- neversight_learn_skills.dev_obviously_awesomeSkill
- process_issuesSkill
- process_prsSkill
- publish-planSkill
- publish_planSkill
- publishSkill
- pullSkill
- pushSkill
- recover_sqlite_databaseSkill
- releaseSkill
- report-errorSkill
- report_errorSkill
- reportSkill
- reviewSkill
- run-feature-workflowSkill
- run_feature_workflowSkill
- setup-commandsSkill
- setup_commandsSkill
- setup-cursor-copiesSkill
- setup_cursor_copiesSkill
- store-neotomaSkill
- store_neotomaSkill
- sync-env-from-1passwordSkill
- sync_env_from_1passwordSkill
- analyzeSkill
- auditSkill
- commitSkill
- create-planSkill
- create-prototypeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Follow foundation/development/feature_unit_workflow.md Step 4 (Checkpoint 2 — Final Review).
- Very specific: line 34
Read foundation-config.yaml to get feature unit settings
- Distinctive: line 39
If compliance check fails: STOP and present compliance report to user
- Distinctive: line 43
If compliance check passes or not available, continue to next step
- Distinctive: line 53
All required tests passing (based on config)
- Distinctive: line 66
STOP and prompt user:
- Distinctive: line 77
Update PR (if applicable)
- Distinctive: line 87
Update repository-specific FU inventory (if configured)
“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.
Files
<!-- Source: foundation/.cursor/skills/final-review/SKILL.md -->name: final-review description: Final review workflow per foundation command. triggers:
- final review
- /final_review
- final-review
Final Review
Present final implementation for review and approval for Feature Unit {{input:feature_id}}.
Follow foundation/development/feature_unit_workflow.md Step 4 (Checkpoint 2 — Final Review). Configuration is read from foundation-config.yaml.
Implements Checkpoint 2 of the Feature Unit creation workflow. Presents the completed implementation for human review and approval.
Trigger
- Implementation complete
- Tests passing
- PR created (if required by config)
Tasks
- Load configuration:
- Read
foundation-config.yamlto get feature unit settings - Determine directory structure, testing requirements, git workflow
- Read
- Run spec compliance validation (if available):
- Execute spec compliance validation script (if repository has one)
- If compliance check fails: STOP and present compliance report to user
- List all gaps found
- Require user to fix gaps, update spec, or explicitly defer requirements before proceeding
- Re-run compliance check after fixes
- If compliance check passes or not available, continue to next step
- Gather implementation summary:
- List all files changed
- List tests added (with pass status)
- List documentation updated
- PR link and status (if PR required)
- Compliance report link (if generated)
- Verify completion:
- All required tests passing (based on config)
- Coverage meets configured targets
- PR created with proper format (if required)
- Spec compliance validation passed (if available)
- Present summary:
- Files changed (count and key files)
- Tests added/passing
- Coverage achieved vs target
- Documentation updated
- PR link (if applicable)
- Spec compliance status (if available)
- STOP and prompt user:
- "Implementation complete. PR: [link]" (if applicable)
- "Please review the implementation"
- "Approve for merge? (yes/no)"
- "Any final changes needed? (list or 'none')"
- "Spec compliance validation: ✅ Pass / ❌ Fail (see report: [link])" (if available)
- If user requests changes:
- Apply changes
- Re-run tests
- Re-run spec compliance validation (if available)
- Update PR (if applicable)
- Repeat until approved
- If approved:
- Mark spec status as
Completed - Move files from
in_progress/tocompleted/:mv {configured_directory}/in_progress/{{input:feature_id}} {configured_directory}/completed/{{input:feature_id}} - Update manifest
status: "completed" - Update repository-specific FU inventory (if configured)
- Mark PR as ready for merge (if applicable)
- If using worktrees (from config), clean up worktree:
# From main repo root git worktree remove {configured_worktree_path} # Or if worktree still has uncommitted changes: git worktree remove --force {configured_worktree_path}
- Mark spec status as
Inputs
feature_id(string): The feature identifier
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
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.

