About Repository Analyzer
Built for engineering leaders, architects, and teams improving the quality of their Git repositories, using curated rule profiles, rich insights, and AI-assisted recommendations.
A shared view of what needs attention
Identify architecture drift, review rule violations with source evidence, and compare saved runs as your code evolves. Use reports to turn technical findings into a conversation about priorities.
What it does
- Analyzes repository structure, projects, and dependencies.
- Runs rule profiles (Basic, Standard, Enterprise) to detect architecture and code-quality issues.
- Provides summaries, trends, and category-level insights for each analysis run.
- Generates source-backed AI architecture insights to highlight risks and recommended improvements.
- Lets you revisit saved runs in Analysis History and ask standards questions in Architecture AI.
- Connects Cursor, VS Code, and GitHub Copilot through MCP so you can discover projects, run analysis, and review findings from the IDE, using the same workspace plans and identity as this site.
How to use it
- Pick a rule profile (or review them on the Profiles & Rules page).
- Go to Analyze Repository and run an analysis for a Git repository.
- Open the summary to review violations, insights, scoring, graph, delta, and AI insights.
- Use Analysis History to reopen prior runs, or ask Architecture AI about governance, standards, modernization, and saved summary context.
- Optionally connect an MCP client in your IDE to run the same analysis from Cursor, VS Code, or Copilot.
IDE analysis via MCP
Repository Analyzer exposes an MCP server so Cursor, VS Code, and GitHub Copilot can discover projects, run governed analysis, generate AI Review, and ask Architecture AI without leaving the editor. MCP uses the same workspace identity, plans, and quotas as this site.
Local IDE use is the supported daily path. Results still appear here in Analysis History.