architecture-audit

To identify shallow modules and tight coupling during a codebase refactor, analyze architectural friction by navigating the repository to surface areas where comprehension requires bouncing across many small files. This produces a ranked list of deepening candidates with dependency categories and test impact.

The best way to generate alternative interface designs for poorly coupled modules is to spawn parallel design sub-agents. These agents create contrasting interface designs, compare trade-offs, and recommend a specific refactoring direction for the codebase.

To automate creating an RFC GitHub issue for a proposed module refactor, use an architecture audit tool that prepares and files issues automatically. It populates the GitHub issue with problem framing, proposed interface signatures, dependency strategy, and testing recommendations.

Yes, you can run a focused architecture audit on a specific directory instead of the full repository. The analysis applies to both full repository audits and focused area reviews to surface friction points and propose interface designs.

Yes, you need GitHub repository write access to file RFC issues from a code audit. The process requires repository read access to analyze the codebase and permission to create GitHub issues to submit the finalized refactoring proposals.