aif-review
Skill0 starsChanged 7 months agoMITView on GitHub
aiframework pre-landing code review with project-specific checks. Checks all invariants, runs specialist reviews based on changed files.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- letuhao/lore-weavetheir own version, first seen Oct 17, 2026
- unxed/f4their own version, first seen Oct 8, 2026
- lee-to/ai-factorytheir own version, first seen Sep 22, 2026
- maister-dev/maistertheir own version, first seen May 27, 2026
- hightemp/go_computer_use_mcp_servertheir own version, first seen Mar 21, 2026
Used with
Projects with it also use aif-explore, aif-qa and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
maister-devSkillaif-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Also in 4 projects that use this
maister-devSkillaif-qa
QA workflow for testing a feature or task implementation. Analyzes changes, produces test plans, and describes concrete test scenarios. Use when user says "test this", "write test plan", "what should I test", or "QA this branch".
Also in 4 projects that use this
letuhaoSkillaif-archive
Archive completed plans and roadmap milestones. Moves finished plans to the archive directory and optionally trims closed milestones from ROADMAP.md. Use when user says \"archive plans\", \"clean up plans\", \"archive completed\", or \"trim roadmap\".
Also in 3 projects that use this
letuhaoSkillaif-qa-check
Executes QA test cases created by $aif-qa in human-guided or automated-agent mode. Use when you need to walk through QA one case at a time, record pass/fail results, or have an agent verify cases through browser, CLI, API, automated tests, or file/document checks.
Also in 3 projects that use this
- +3 more from maister-dev
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- lee-to/ai-factory★ 1.2ksame name
- unxed/f4★ 261same name
- letuhao/lore-weave★ 35same name
- maister-dev/maister★ 10same name
- hightemp/go_computer_use_mcp_server★ 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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- aif-analyzeSkill
- aif-enhanceSkill
- aif-evolveSkill
- aif-feedbackSkill
- aif-ingestSkill
- aif-learnSkill
- aif-pulseSkill
- aiframework-learnSkill
- aiframework-reviewSkill
- aiframework-shipSkill
- aif-readySkill
- aif-researchSkill
- aif-shipSkill
- aif-statusSkill
- retroSkill
- sheal-askSkill
- sheal-checkSkill
- sheal-driftSkill
- sheal-retroSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Verify no raw SQL, all queries through ORM, migrations are reversible.
- Distinctive: line 31
Look for: raw SQL strings, missing migrations, schema changes without migration.
- Distinctive: line 34
Verify LLM output is never trusted as safe.
- Distinctive: line 35
Look for: unsanitized AI output in HTML, eval of AI-generated code, AI output in SQL.
- Very specific: line 41
Check tools/review-specialists/ for domain-specific review checklists.
- Distinctive: line 52
If vault/ exists, check for related decisions:
- Very specific: line 53
Read vault/memory/decisions/ for ADRs related to changed files
- Very specific: line 54
Run vault/.vault/scripts/vault-tools.sh lint to verify vault integrity
“Common” is measured: kept by at least 6 in 10 of the 5 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
/aif-review — Code Review
Step 0: Telemetry (silent, non-blocking)
aiframework-telemetry skill_invoked skill=aif-review 2>/dev/null || trueStep 1: CRITICAL Pass
For each changed file (git diff --name-only HEAD~1 HEAD), check:
1.1 INV-1: Database Safety
Verify no raw SQL, all queries through ORM, migrations are reversible. Look for: raw SQL strings, missing migrations, schema changes without migration.
1.2 INV-2: LLM Trust Boundary
Verify LLM output is never trusted as safe. Look for: unsanitized AI output in HTML, eval of AI-generated code, AI output in SQL.
Step 2: Specialist Army (if applicable)
Launch parallel specialists based on what files changed.
Check tools/review-specialists/ for domain-specific review checklists.
Step 3: Report
Output a table:
| Check | Status | Details |
| ... | PASS/FAIL/WARN | ... |
Step 4: Vault Check
If vault/ exists, check for related decisions:
- Read
vault/memory/decisions/for ADRs related to changed files - Run
vault/.vault/scripts/vault-tools.sh lintto verify vault integrity
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.

