architect-review
Skill8 starsChanged 6 months agoMITView on GitHub
Review code changes for architectural issues — module boundaries, coupling, and dependency direction.
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
- hlhr202/swe-skills★ 3same 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 repository16 other files it gives its agents.
- .claude/rules/common/agents.mdAGENTS.md
- agent-creatorSkill
- build-fixSkill
- code-reviewSkill
- deep-diveSkill
- docsSkill
- incident-debugSkill
- performance-reviewSkill
- planSkill
- qaSkill
- ralphSkill
- refactor-cleanSkill
- rule-creatorSkill
- security-reviewSkill
- skill-creatorSkill
- tdd-workflowSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
2
Distinctive
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 13
If arguments are provided (file paths or PR number), use those as scope
- Distinctive: line 15
Run git log --oneline -5 for recent commit context
“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
Spawns the architect-reviewer agent to analyze your current changes at the system level — module boundaries, dependency direction, and pattern consistency.
Steps
- Gather context — detect the scope of changes to review:
- If arguments are provided (file paths or PR number), use those as scope
- Otherwise, use
git diff --name-onlyto determine which modules are affected - Run
git log --oneline -5for recent commit context
- Spawn the agent — use the Task tool:
Pass in the prompt:Task tool with subagent_type="architect-reviewer"- The diff output and list of changed files
- The module/directory structure of the project
- Any architectural conventions from
.claude/rules/that apply
- Present findings — relay the agent's architecture review:
- Group by severity: VIOLATION > WARNING > SUGGESTION
- Include module names and dependency chains
- Show recommended fixes for boundary violations
- Offer follow-up actions:
- "Fix violations?" — restructure imports to respect boundaries
- "Run code review too?" — spawn code-reviewer for line-level feedback
- "Review again?" — re-run after changes
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.