review-architecture
Skill8 starsChanged 5 months agoMITView on GitHub
Use when a change affects architecture, reuse, data ownership, module boundaries, dependencies, security, migration, or refactor pressure.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- unlockers-ai/unlockers-skills-librarytheir own version, first seen Nov 8, 2026
- pascalorg/editortheir own version, first seen Nov 6, 2026
- dotnet/orleanstheir own version, first seen Nov 1, 2026
- rpraharaj/ai-sdlctheir own version, first seen Nov 1, 2026
- ROCm/rocprofiler-systems-skillstheir own version, first seen Oct 27, 2026
- nesnilnehc/ai-cortextheir own version, first seen Oct 25, 2026
Used with
Projects with it also use review-testing, review-correctness and 1 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.
worldbankSkillreview-testing
Review test code for quality, design, and completeness after implementing a feature or fixing a bug. Use when the user asks to "review my tests", "check my test quality", "are these tests good enough", "review testing", or after completing a feature implementation that includes tests. Also use when tests feel brittle, flaky, or superficial. Cross-references production code to find coverage gaps.
Also in 4 projects that use this
navjyotnishantSkillreview-correctness
Use this skill when the user asks to "review my changes for bugs", "check this diff for correctness", "did I introduce a regression", or wants a correctness-focused review of the current commit or uncommitted work before pushing. Reviews the changed lines and their blast radius for logic errors, regressions, unhandled edge cases, and missing validation. Works in any git repo; nothing here is project-specific.
Also in 3 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- pascalorg/editor★ 26ksame name
- dotnet/orleans★ 11ksame name
- daveallie/crosspoint-reader★ 8.8ksame name
- crosspoint-reader/crosspoint-reader★ 8.8ksame name
- apache/pinot★ 6.2ksame name
- mrinalwadhwa/fluent★ 125same name
- dannys-code-corner/incan★ 74same name
- igmarin/rails-agent-skills★ 26same name
- nesnilnehc/ai-cortex★ 8same name
- ROCm/rocprofiler-systems-skills★ 5same 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- apply-wiki-changeSkill
- compile-changeSkill
- generate-checksSkill
- import-codebaseSkill
- propose-changeSkill
- reconcile-wikiSkill
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 10
Prefer the smallest refactor that makes the change safe.
- Very specific: line 14
Read references/architecture-review-rubric.md before producing the review.
“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
Review Architecture
Your job is to decide whether the current architecture can absorb the change cleanly. You are not here to invent a large redesign. Prefer the smallest refactor that makes the change safe.
Review questions
Read references/architecture-review-rubric.md before producing the review.
- Which existing capability should be reused?
- Would this create a duplicate path?
- Which module owns the data?
- Which interface or contract changes?
- Does this cross a trust boundary?
- Does this add a special case to a module that is already too broad?
- Is a preparatory refactor needed first?
- What is the rollback path?
Output
Return:
- Reuse recommendation.
- Boundary and dependency risks.
- Refactor pressure: low, medium, high.
- Security or data concerns.
- Required checks.
- Recommendation: proceed, proceed with small refactor, or stop and write a refactor proposal.
Related skills
compile-change: when the review is part of implementation.propose-change: when the review finds a refactor or product decision that needs approval.
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.

