23 tagged architecture-review, measured the same way as everything else here.
Browse within: aec 33antigravity 33bim 33building-ai 33balanced-coupling 18codex-cli 18claude-code-plugin 9clean-architecture 9code-quality 9tech-debt 9adr 7architectural-decision-records 7architecture 7claude-plugin 7
Skill Claude CodeCodex
End-to-end project, artifact, and code review for assessing completion, requirements coverage, architecture, implementation quality, testing, risks, documentation, readiness, and improvement opportunities. Use when Codex needs to audit a software or technical project, review a diff or PR, judge whether work is…
Skill Claude CodeCodex
Run a substantive idea, draft, design, architecture, strategy, or decision through a modular Council → Chair → Executor → Reviewer workflow. Use when the user asks to council, develop, pressure-test, stress-test, poke holes in, strengthen, review, synthesize, create an implementation plan, or turn a complex set of…
Skill Claude CodeCodex
Assess coupling with the Balanced Coupling model (integration strength, distance, volatility). Use when judging whether coupling is balanced or risky, scoring the couplingbalance dimension, or deciding what to flag as structural risk. Highest risk is high strength + high distance + high volatility together. NOT…
Skill Claude CodeCodex
Gather deterministic architecture-fitness evidence with archfit: full checks, scorecards, deltas, SARIF/JSON findings, tool coverage, and agenttasks. Use when a repo has .archfit.yaml or the user wants architect to combine its review with archfit. Produces hard facts for architecture-review to calibrate, not a…
Skill Claude CodeCodex
Gather local codebase evidence with fd, rg, git grep, git log, and targeted file reading. Use when starting an architecture review, building the system map, finding entrypoints, locating module boundaries, tracing exact text or config keys, or collecting file:line evidence for modularity, coupling, dependency…
Skill Claude CodeCodex
A guided interview for testing plans and comparing refactoring options, with the decisions exported as an interactive HTML form.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: