agentleFS
conectlensconectlens/lenserfight/.agents/skills/repo-architecture-auditor/SKILL.md

repo-architecture-auditor

Skill18 starsChanged 6 months agoMITView on GitHub

Audit Nx monorepo structure, layer responsibilities, dependency drift, public APIs, and misplaced logic. Use for architecture review, library placement, boundary erosion, duplication, and repo health checks.

The file

Files
SKILL.md

Repo Architecture Auditor

Use when

  • the repo structure feels unclear, duplicated, or layered incorrectly
  • a refactor may move logic across apps, libs, or supabase
  • you need an architecture map, hotspot list, or cleanup plan

Workflow

  1. Map the current layer responsibilities and detect boundary drift.
  2. Identify duplicated capabilities, leaky abstractions, and oversized libraries.
  3. Produce a prioritized action plan with rationale and target locations.

Load only when needed

  • Architecture review method
  • Audit report template

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.