agentleFS
markmhendricksonmarkmhendrickson/neotoma/.claude/skills/final_review/SKILL.md

final_review

Skill38 starsChanged 2 months agoMITView on GitHub

Final Review

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    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
  1. Very specific:

    Follow foundation/development/feature_unit_workflow.md Step 4 (Checkpoint 2 — Final Review).

    line 13
  2. Very specific:

    Read foundation-config.yaml to get feature unit settings

    line 26
  3. Distinctive:

    If compliance check fails: STOP and present compliance report to user

    line 31
  4. Distinctive:

    If compliance check passes or not available, continue to next step

    line 35
  5. Distinctive:

    All required tests passing (based on config)

    line 45
  6. Distinctive:

    STOP and prompt user:

    line 58
  7. Distinctive:

    Update PR (if applicable)

    line 69
  8. Distinctive:

    Update repository-specific FU inventory (if configured)

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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
<!-- Source: .cursor/skills/final-review/SKILL.md -->

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

  1. Load configuration:
    • Read foundation-config.yaml to get feature unit settings
    • Determine directory structure, testing requirements, git workflow
  2. 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
  3. 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)
  4. 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)
  5. 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)
  6. 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)
  7. If user requests changes:
    • Apply changes
    • Re-run tests
    • Re-run spec compliance validation (if available)
    • Update PR (if applicable)
    • Repeat until approved
  8. If approved:
    • Mark spec status as Completed
    • Move files from in_progress/ to completed/:
      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}

Inputs

  • feature_id (string): The feature identifier

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.