Review tutti git diffs for project structure, layering, module ownership, and duplicate event-center infrastructure by planning focused architecture review tasks, then having the main agent orchestrate sub-agents for only the changed areas.
SkillScore74Maintained
Automatic
◆Coding pack
Last verified 8/29/2026
What it changes
Passed 13 of 18 test cases with the skill, and 3 of 18 without it.
Without skill17%
With skill74%
Checks it passed that the model alone missed
Runs plan-review.mjs using node.
Includes the --format summary flag.
Cites file paths for reported findings.
and 18 more in the full report
14 fixed3 passed either way5 still failing1 broke
Pass-rate lift
+57 pp
Tokens
+67%
Agent turns
0%
Response time
-54%
Model gemini-3.6-flashMeasured 8/29/2026v117 of 23 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
After running plan-review.mjs with automatic temporary file output, which JSON property contains the saved package file path?
What was checked, without and with the skill
Checked
Without skill
With skill
Reads the path from workflowEntry.packagePath.
Missed
Passed
case-22 · gemini-3.6-flash · 8/29/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md164 lines8 filesincludes scripts
Tutti Architecture Review
Use this skill when reviewing a tutti change or a named module for repository structure, module ownership, or layering compliance. This is a focused architecture review, not a general bug hunt.
Vocabulary
Use the architecture vocabulary consistently:
Module: anything with an interface and an implementation.
Interface: everything a caller must know to use the module correctly.
Implementation: the code inside a module.
Depth: leverage at the interface; deep modules hide useful behavior behind a small interface.
Seam: where an interface lives.
Adapter: a concrete thing satisfying an interface at a seam.
Leverage: what callers get from depth.
Locality: what maintainers get from depth.
Prefer these words in findings. Avoid vague substitutes such as "component", "service", "utility", or "boundary" when a vocabulary term fits.
Workflow
Resolve the user's review intent:
plain git diff review for the current change
module-focused diff review when the user names a module inside the current change
static module review when the user wants a named module inspected even without current diff overlap
Use light natural-language guidance when the request is ambiguous. Do not force the user through a fixed mode menu.
When the user names a module, let the main agent infer a few candidate path keywords and gather candidate paths. Then normalize those paths into a scope file:
Candidate input is agent-produced. The script does not invent module keywords or search the repository itself; it only normalizes candidate paths into a stable scope contract for the planner.
Read references/scope-contract.md when changing or consuming the candidate input, normalized scope output, or planner scope metadata.