agentleFS
omarismailbomarismailb/product-wiki/.agents/skills/review-architecture/SKILL.md

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

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.
  • worldbankSkill

    review-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

  • navjyotnishantSkill

    review-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

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 3 projects that use this

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
  1. Distinctive:

    Prefer the smallest refactor that makes the change safe.

    line 10
  2. Very specific:

    Read references/architecture-review-rubric.md before producing the review.

    line 14

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.