architecture-audit

You can automate codebase audits by running the architecture-audit skill, which walks through your project to identify architectural friction and files each deepening opportunity as a triageable GitHub issue.

The three-lens approach for code architecture analysis evaluates a codebase from three distinct perspectives: Locality, Testability, and Vocabulary, using a predefined architecture vocabulary to categorize findings.

Yes, you can use architecture audit with your existing GitHub repository, as it requires a GitHub repository and the kamp-us/phoenix architecture vocabulary to operate and file issues.

No, the code audit process operates in a read-only mode and does not modify your codebase, ensuring your source files remain untouched while it identifies architectural issues and files GitHub issues.

To triage architectural friction found during a code audit, the skill automatically files each identified opportunity as a separate GitHub issue, allowing your team to review and track code quality improvements.

Yes, you need the kamp-us/phoenix architecture vocabulary to audit code quality, as the skill uses this predefined vocabulary to ensure consistency when analyzing and reporting architectural findings.