agentleFS
sainzssainzs/santiagosainz-skills/skills/core/architecture-review/SKILL.md

architecture-review

Skill1 starsChanged 3 months agoMITView on GitHub

Review architecture for maintainability risks, boundary leaks, naming drift, shallow modules, missing contracts, and staged refactors. Use when the user asks to review architecture, simplify architecture, reduce coupling, or use architecture-pass.

85 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done and 10 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.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 77 edited versions we read keep these.

  • 7

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

    Do one job: identify structural risk and the next reversible architecture move.

    line 12
  2. Distinctive:

    Prefer small composable modules with text-visible contracts over hidden orchestration.

    line 14
  3. Distinctive:

    Do not invent a new framework when a boundary, name, or test contract fixes the pressure.

    line 15
  4. Distinctive:

    Stop at ranked candidates unless implementation is explicitly requested.

    line 16
  5. Distinctive:

    Use for architecture review, codebase simplification, module boundary cleanup, dependency direction, duplicated concepts, and testability …

    line 20
  6. Distinctive:

    Stop after the top risks are clear.

    line 32
  7. Distinctive:

    Do not perform a broad refactor unless the user explicitly asks for implementation.

    line 54

“Common” is measured: kept by at least 6 in 10 of the 77 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

architecture-review

Find the smallest structural moves that improve future change.

Unix/Pi Contract

  • Do one job: identify structural risk and the next reversible architecture move.
  • Consume interfaces, callers, tests, docs, and dependency evidence; emit ranked risks and staged refactors.
  • Prefer small composable modules with text-visible contracts over hidden orchestration.
  • Do not invent a new framework when a boundary, name, or test contract fixes the pressure.
  • Stop at ranked candidates unless implementation is explicitly requested.

Use

Use for architecture review, codebase simplification, module boundary cleanup, dependency direction, duplicated concepts, and testability gaps.

Research Budget

Inspect:

  1. Public entrypoints and interfaces.
  2. Callers and dependency direction.
  3. Tests and verification gates.
  4. ADRs, glossary, and docs for intended boundaries.
  5. Repeated names, config paths, and error handling.

Stop after the top risks are clear.

Review Lenses

  • Ownership: who owns this behavior and where should changes land?
  • Boundary: which imports, data shapes, or side effects cross layers awkwardly?
  • Coupling: what hidden ordering, global state, config, or environment assumptions exist?
  • Depth: which modules expose too much choreography through a shallow interface?
  • Duplication: which concepts are implemented more than once with different names?
  • Proof: what contract tests or smoke checks are missing?
  • Migration: what is the smallest reversible refactor path?

Output

Return:

  1. Ranked risks with file evidence.
  2. User or maintainer cost.
  3. Small staged refactors.
  4. Tests or checks to add.
  5. Recommended first move.

Do not perform a broad refactor unless the user explicitly asks for implementation.

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.