AI-powered GitHub Repository Health Analyzer
Built with the GitHub Copilot SDK β the same AI agent runtime that powers Copilot CLI.
Website β’ Quick Start β’ Features β’ How It Works β’ Commands β’ Documentation
RepoCheckAI is your repository's AI doctor that diagnoses issues and prescribes solutions. It performs comprehensive health checks across 6 critical areas β documentation, developer experience, CI/CD, testing, governance, and security β delivering a detailed diagnosis with prioritized findings (P0/P1/P2) and actionable remediation steps.
| Mode | Description | Use Case |
|---|---|---|
| π Quick Scan | Analyzes via GitHub API (up to 20 file reads) | Fast checks, governance review |
| π¬ Deep Analysis | Full source scan using Repomix | Code quality, architecture review |
|
|
|
|
|
Automatically publish analysis reports to GitHub as structured issues:
export GITHUB_TOKEN=ghp_xxx # or REPOCHECKAI_GITHUB_TOKEN, as configured
repocheck analyze owner/repo --issue
# Creates: π΄ [RepoCheckAI] docs: Missing README
# π [RepoCheckAI] ci: No CI/CD Pipeline
# π‘ [RepoCheckAI] dx: Code Quality IssuesEach issue includes:
- Detailed description with evidence and impact assessment
- Actionable fix instructions with code examples
- Priority labels (P0/P1/P2) and category tags
- Full analysis context for team collaboration
# Set token securely (recommended)
export GITHUB_TOKEN=ghp_your_token_here
# Or use gh CLI auth
gh auth login
# Then start interactive mode
repocheck chat
/analyze facebook/react --issue
/deep microsoft/vscodeTip
Perfect for automated repository health tracking and team collaboration!
π Learn how to set up GitHub tokens
Want to see RepoCheckAI create GitHub issues automatically?
# 1. Get a GitHub token (see detailed setup below)
# 2. Set it as environment variable
export GITHUB_TOKEN=ghp_your_token_here
# 3. Analyze and create issues automatically!
repocheck analyze your-username/your-repo --issueResult: Multiple GitHub issues created with detailed analysis, impact assessment, and fix instructions! π
For the --issue feature, you'll need a GitHub Personal Access Token with specific permissions:
- Go to github.com/settings/tokens
- Generate a new "Tokens (classic)"
- Select these scopes:
repo(full repository access) OR the following granular permissions:metadataβ Read repository metadatacontentsβ Read repository contentsissuesβ Create and manage issues
- Copy the token (starts with
ghp_)
--issue (CLI) and Publish to GitHub Issues (Web UI) both need GitHub API credentials with issue-write permission.
export GITHUB_TOKEN=ghp_your_pat_here
repocheck analyze owner/repo --issuenpm run dev:local-uiIn the form:
- Enable
Publish to GitHub Issues - Optional: paste
GitHub Token(overrides server env token) - Run analysis
If no token is provided in the field, the backend uses GITHUB_TOKEN from the server environment.
For full step-by-step setup and 401/403 troubleshooting, see docs/issue-publishing.md.
| Category | What's Checked | Example Findings |
|---|---|---|
| π Docs & Onboarding | README, setup instructions, contributing guidelines | Missing installation steps |
| β‘ Developer Experience | Build scripts, language version, project structure | No .nvmrc or .node-version |
| π CI/CD | GitHub Actions, test automation, build pipelines | No CI workflow found |
| π§ͺ Quality & Tests | Test framework, linting, formatting, coverage | Missing test configuration |
| π Governance | LICENSE, CODE_OF_CONDUCT, SECURITY policy | No LICENSE file |
| π Security | Dependabot/Renovate, security policy, secret scanning | No dependency updates configured |
Important
- GitHub Copilot β Active subscription required
- Node.js β Version 18.0.0 or higher
# Clone the repository
git clone https://github.com/glaucia86/repocheckai.git
cd repocheckai
# Install dependencies and build
npm install
npm run build
# Link globally
npm link# Interactive mode
repocheck
# Direct analysis
repocheck vercel/next.js
# Deep analysis with premium model
repocheck vercel/next.js --model claude-sonnet-4 --deep
# π Auto-create GitHub issues for each problem found
repocheck vercel/next.js --issueNote
--issue requires a GitHub token. Learn how to set it up.
| Command | Description |
|---|---|
/analyze <repo> |
Quick analysis via GitHub API |
/deep <repo> |
Deep analysis with full source scan |
/copy |
Copy last report to clipboard |
/export [path] |
Save report as markdown file |
/model [name] |
Switch AI model (now works in onboarding phase) |
/help |
Show all available commands |
/quit |
Exit RepoCheckAI |
Tip
Use /deep for comprehensive code quality analysis. Use /analyze for quick governance checks.
The repository keeps application runtime code in src/ and the public website in site/:
site/ # Static marketing/docs site deployed to GitHub Pages
src/ # Clean architecture runtime code
Implementation source is now organized by clean architecture layers in src/:
- Presentation:
src/presentation/**(CLI, API, Web UI, terminal UI) - Application:
src/application/**(analysis and reporting orchestration) - Infrastructure:
src/infrastructure/**(GitHub/providers/tools adapters) - Domain:
src/domain/**(schemas, contracts, interfaces) - Shared utilities:
src/utils/**
The project has a single Web UI implementation served from src/presentation/web/public by src/presentation/web/main.ts.
npm run dev:web-ui:api
npm run dev:web-uiOr run both services together:
npm run dev:local-uiCurrent MVP capabilities:
- Create analysis jobs from web state/client modules
- Read completed markdown/JSON reports
- Stream progress seeds and cancel running jobs
- Copy and export completed reports (
mdandjson)
repocheck
/analyze microsoft/vscoderepocheck
/model claude-sonnet-4
/deep facebook/reactrepocheck
/analyze vercel/next.js
/export nextjs-report.mdrepocheck
# Then use commands interactively
/analyze myorg/myrepo
/copy| Model | Type | Best For |
|---|---|---|
gpt-4o |
Free | Balanced performance (default) |
gpt-4.1 |
Free | Fast analysis |
gpt-5.4 |
Premium β‘ | Latest GPT capabilities |
gpt-5.3-codex |
Premium β‘ | Advanced coding tasks |
claude-sonnet-4 |
Premium β‘ | Detailed analysis |
claude-opus-4.5 |
Premium β‘ | Most capable (3x rate limit) |
o3 |
Premium β‘ | Deep reasoning tasks |
Note
Premium models require GitHub Copilot Pro/Enterprise. See AI Models Guide for full list.
| Document | Description |
|---|---|
| οΏ½ Getting Started | Installation and first analysis |
| π User Guide | Complete usage guide with examples |
| π» Commands | Full CLI command reference |
| π Analysis Categories | What gets analyzed in each category |
| π€ AI Models | Available models and recommendations |
| ποΈ Architecture | Technical architecture and design |
| β FAQ | Frequently asked questions |
| π§ Troubleshooting | Common issues and solutions |
| π€ Contributing | How to contribute to RepoCheckAI |
π Full documentation: docs/index.md
|
Copilot SDK AI Orchestration |
Octokit GitHub API |
Repomix Repo Packing |
TypeScript Language |
Zod Validation |
The codebase follows SOLID principles for maintainability:
src/
βββ cli/ # Command handlers, state, parsers
βββ core/agent/ # Copilot SDK session, modular prompts
βββ tools/ # Individual tool files (SRP)
βββ ui/display/ # Display modules (spinner, menus, etc.)
βββ types/ # Zod schemas, interfaces
Key Design Decisions:
- Agentic CLI: Uses GitHub Copilot SDK for AI-powered analysis
- Modular Prompts: System prompts composed from reusable base modules
- Tool-Based Architecture: AI agent invokes specific tools for data gathering
- Streaming Output: Real-time analysis with event-driven updates
- Security First: Content sanitization prevents prompt injection
π See Architecture Documentation for technical details.
If you find RepoCheckAI useful:
| β Star this repository | π Report issues you encounter |
| π‘ Suggest new features | π Contribute via pull requests |
MIT Β© Glaucia Lemos
Made with π using the GitHub Copilot SDK
