agentleFS
20030419zhanghongyi20030419zhanghongyi/AI-Software-Engineering-Workflow-Template/.claude/skills/review-artifact/SKILL.md

review-artifact

Skill0 starsChanged 6 months agoMITView on GitHub

Prepare a compact Review Artifact before merge decisions.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Read only the files above.

    line 40
  2. Distinctive:

    Ask for Human Owner review and stop.

    line 43
  3. Distinctive:

    Test result is missing

    line 53

≈ “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

Review Artifact

Purpose

Generate a Review Artifact for Review Gate.

When to use

  • Implementation is complete
  • A PR or diff needs structured review
  • Merge should be evaluated but not executed

Read first

  • AI_WORKFLOW.md
  • docs/11_stage_gates.md
  • docs/13_human_gate_and_rollback.md
  • .ai/artifacts/REVIEW_ARTIFACT_TEMPLATE.md

Inputs

  • git diff
  • Implementation Report
  • Test results
  • Relevant architecture or boundary docs

Outputs

  • Review Artifact
  • Merge recommendation

Steps

  1. Confirm the task is in Review Gate.
  2. Read only the files above.
  3. Summarize diff, architecture impact, boundary check, tests, and risks.
  4. Fill the Review Artifact with a merge recommendation.
  5. Ask for Human Owner review and stop.

Human review

Human Owner must review the artifact and choose whether to merge, request changes, rollback, or abandon.

Stop conditions

  • Information is insufficient
  • File boundary is unclear
  • Test result is missing
  • Rollback thinking is missing
  • User has not approved the review step
  • Any action would auto merge / release / push / commit

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.