review-artifact
Skill0 starsChanged 6 months agoMITView on GitHub
Prepare a compact Review Artifact before merge decisions.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/ai-coding-rules.mdcCursor rule
- .cursor/rules/architecture-rules.mdcCursor rule
- .cursor/rules/project-rules.mdcCursor rule
- implementation-reportSkill
- launch-checkSkill
- mvp-scope-checkSkill
- plan-from-issueSkill
- review-artifactSkill
- scale-automation-reviewSkill
- validate-ideaSkill
- implementation-reportSkill
- launch-checkSkill
- mvp-scope-checkSkill
- plan-from-issueSkill
- scale-automation-reviewSkill
- validate-ideaSkill
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
- Distinctive: line 40
Read only the files above.
- Distinctive: line 43
Ask for Human Owner review and stop.
- Distinctive: line 53
Test result is missing
≈ “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.
Files
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
- Confirm the task is in Review Gate.
- Read only the files above.
- Summarize diff, architecture impact, boundary check, tests, and risks.
- Fill the Review Artifact with a merge recommendation.
- 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
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.

