agentleFS
cobusgreylingcobusgreyling/grok-build-arsenal/skills/architecture-reviewer/SKILL.md

architecture-reviewer

Skill6 starsChanged 6 months agoMITView on GitHub

Perform focused architecture and modularity reviews. Identify boundary violations, god objects, tangled dependencies, and propose the smallest reversible improvements. Use the repo-graph MCP when available. Trigger with "architecture review", "check the boundaries", "is this modular enough?".

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always pair recommendations with a plan (hand off to plan-mode-orchestrator).

    line 22
  2. Very specific:

    Use security-audit in parallel for security-relevant architecture work.

    line 35

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

Keeps large codebases from turning into big balls of mud.

Process

  1. Get a structural view (use repo-graph MCP or manual exploration + subagents).
  2. Map current modules and data flow.
  3. Identify:
    • Unclear or violated boundaries
    • High coupling / low cohesion
    • Missing abstractions
    • Opportunities for ports/adapters or domain-driven splits
  4. Propose the smallest change that meaningfully improves the situation.
  5. Always pair recommendations with a plan (hand off to plan-mode-orchestrator).

Output Format

  • Current state summary (with diagram if possible)
  • Specific problems with file/line evidence
  • Recommended improvement + rationale
  • Risk of the change
  • How to verify the improvement (usually via tests + repo-graph diff)

Ties to Other Skills

  • Works extremely well after or with subagent-arena.
  • Feeds directly into plan-mode-orchestrator.
  • Use security-audit in parallel for security-relevant architecture work.

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.