hotplex-arch-analyzer

To find architecture issues in a Go gateway, run progressive analysis covering SOLID, coupling, concurrency safety, and performance to identify high-ROI problems and track them via GitHub issues.

Maintaining a healthy issue backlog for large repositories uses an audit mode that validates, closes, or updates outdated and false-positive architecture issues when open issue counts reach a threshold.

Yes, you can resume architecture analysis after an interruption because progress is persisted in a JSON matrix file, allowing looped inspection cycles to recover and continue covering remaining modules.

Preventing duplicate GitHub issues during code quality audits requires de-duplication logic that checks module, file, location, and aspect semantics to merge overlapping findings into a single issue.

Subagent-based code analysis reduces context window consumption by delegating source reading and deep inspection to subagents, passing only structured JSON results back to the main session.

You should switch from issue creation to audit mode for security audits when the number of open architecture issues reaches a predefined threshold, triggering validation of existing backlog entries.