architect-review
Skill3 starsChanged 2 months agoApache-2.0View on GitHub
Review Architect track work or explicit current changes against project context, track intent, style guides, and tests. Use when the user asks to review, verify, audit, inspect, approve, or apply review fixes for Architect-managed work.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- aiqianqian521/architect-skillstheir own version, first seen Nov 1, 2026
- ya222/skillforgetheir own version, first seen Oct 20, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- Tgoldi/claude-skillstheir own version, first seen Oct 13, 2026
- prestarius/jet-skills-stacktheir own version, first seen Oct 11, 2026
- garthcodes/claude-skillstheir own version, first seen Oct 8, 2026
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- kumaran-is/claude-code-onboarding★ 35same name
- xfstudio/skills★ 9same name
- bis-code/claude-toolkit★ 8same name
- ai4brands-design/claude-skills★ 2same name
- Aver005/agent-skills★ 2same name
- garthcodes/claude-skills★ 2same name
- aiqianqian521/architect-skills★ 1same name
- alex-macra/claude-codex-skills-assembly★ 1same name
- aptitude-stack/registery★ 1same name
- aptitude-stack/resolver★ 1same name
5 more not listed
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 repository5 other files it gives its agents.
- architect-discussSkill
- architect-implementSkill
- architect-proposeSkill
- architect-setupSkill
- architect-statusSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Commit, archive, or delete only with the protocol's explicit authorization.
- Very specific: line 19
Read references/review-protocol.md and classify track versus non-track scope.
“Common” is measured: kept by at least 6 in 10 of the 14 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
Architect Review
Perform a findings-first principal-engineer review of a track or explicit change scope. Follow references/review-protocol.md as the source of truth.
Hard Boundaries
- Require Architect context for track review; warn before limited non-track review without it.
- Adopt exact or high-confidence scope without reconfirmation; ask once only for ambiguity.
- A review request does not authorize fixes.
Apply Fixesauthorizes only reported findings. - Commit, archive, or delete only with the protocol's explicit authorization.
Run
- Read
references/review-protocol.mdand classify track versus non-track scope. - Adopt or confirm scope once, load applicable context, and derive the diff with recorded confidence.
- Review plan, product, stack, style, correctness, security, maintainability, and tests.
- Return findings first, ordered by severity, with verification and residual risk.
- Apply and record only authorized fixes.
- Offer cleanup only for an eligible track and require exact confirmation for destructive actions.
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.