diff --git a/AGENTS.md b/AGENTS.md index 57626c8..7185cae 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,4 +1,4 @@ -# AGENTS.md — Repo Doctor +# AGENTS.md — Repo Check AI AI-powered GitHub repository health analyzer using the GitHub Copilot SDK. @@ -21,3 +21,4 @@ npm run build # Production build - **Security**: Content sanitized via `utils/sanitizer.ts` For detailed documentation, see [docs/index.md](docs/index.md). + diff --git a/CHANGELOG.md b/CHANGELOG.md index ebb1d6d..88ea385 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] +### Added + +- **Migration Communication**: Added official announcement at `docs/announcements/repocheckai-migration.md`. + +### Changed + +- **Project Identity Migration**: Official project identity is now `RepoCheckAI`. +- **CLI Command Policy**: `repocheck` is now the official command, while `repodoctor` remains temporarily available with deprecation warning. +- **Transition Window**: Legacy command support is scheduled for two releases (`2.5.0` through `2.6.x`). + --- ## [2.5.0] - 2026-02-14 @@ -69,11 +79,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Added -- **CLI**: Support for `/model` command in onboarding phase ([#123](https://github.com/glaucia86/repo-doctor/pull/123)) +- **CLI**: Support for `/model` command in onboarding phase ([#123](https://github.com/glaucia86/repocheckai/pull/123)) ### Fixed -- **CLI**: Fixed `/model` command requiring double input in onboarding phase ([#124](https://github.com/glaucia86/repo-doctor/pull/124)) +- **CLI**: Fixed `/model` command requiring double input in onboarding phase ([#124](https://github.com/glaucia86/repocheckai/pull/124)) --- @@ -102,20 +112,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Breaking Changes -- **Infinite Sessions API**: Updated to Copilot SDK v0.1.18. Custom integrations using session management may need to handle new compaction events ([#104](https://github.com/glaucia86/repo-doctor/pull/104)) -- **Theme System**: Modular theme system introduced. Custom themes may need to be updated to use new module structure ([#105](https://github.com/glaucia86/repo-doctor/pull/105)) +- **Infinite Sessions API**: Updated to Copilot SDK v0.1.18. Custom integrations using session management may need to handle new compaction events ([#104](https://github.com/glaucia86/repocheckai/pull/104)) +- **Theme System**: Modular theme system introduced. Custom themes may need to be updated to use new module structure ([#105](https://github.com/glaucia86/repocheckai/pull/105)) ### Changed -- **Issue Publishing**: Improved priority label handling in `publishReport.ts` (removed unnecessary `.toLowerCase()`) ([#106](https://github.com/glaucia86/repo-doctor/pull/106)) -- **Documentation**: Enhanced `--issue` feature documentation with setup instructions and 401 troubleshooting ([#107](https://github.com/glaucia86/repo-doctor/pull/107)) -- **Documentation**: Updated AI model recommendations, highlighting Claude Sonnet 4.5 for best report quality with `--issue` ([#108](https://github.com/glaucia86/repo-doctor/pull/108)) -- **Documentation**: Improved token handling instructions for security best practices ([#109](https://github.com/glaucia86/repo-doctor/pull/109)) -- **Documentation**: Updated interactive mode instructions for secure token handling ([#110](https://github.com/glaucia86/repo-doctor/pull/110)) +- **Issue Publishing**: Improved priority label handling in `publishReport.ts` (removed unnecessary `.toLowerCase()`) ([#106](https://github.com/glaucia86/repocheckai/pull/106)) +- **Documentation**: Enhanced `--issue` feature documentation with setup instructions and 401 troubleshooting ([#107](https://github.com/glaucia86/repocheckai/pull/107)) +- **Documentation**: Updated AI model recommendations, highlighting Claude Sonnet 4.5 for best report quality with `--issue` ([#108](https://github.com/glaucia86/repocheckai/pull/108)) +- **Documentation**: Improved token handling instructions for security best practices ([#109](https://github.com/glaucia86/repocheckai/pull/109)) +- **Documentation**: Updated interactive mode instructions for secure token handling ([#110](https://github.com/glaucia86/repocheckai/pull/110)) ### Fixed -- **Priority Labels**: Ensured consistent case handling for issue priority labels ([#111](https://github.com/glaucia86/repo-doctor/pull/111)) +- **Priority Labels**: Ensured consistent case handling for issue priority labels ([#111](https://github.com/glaucia86/repocheckai/pull/111)) --- @@ -180,17 +190,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Breaking Changes -- **Internal Architecture**: Major refactoring following SOLID principles. Contributors extending the codebase may need to update imports and class structures ([#95](https://github.com/glaucia86/repo-doctor/pull/95)) -- **CLI Module Structure**: Extracted CLI components into separate modules. Custom CLI integrations may require import path updates ([#96](https://github.com/glaucia86/repo-doctor/pull/96)) +- **Internal Architecture**: Major refactoring following SOLID principles. Contributors extending the codebase may need to update imports and class structures ([#95](https://github.com/glaucia86/repocheckai/pull/95)) +- **CLI Module Structure**: Extracted CLI components into separate modules. Custom CLI integrations may require import path updates ([#96](https://github.com/glaucia86/repocheckai/pull/96)) ### Added -- **Agent Guardrails**: Loop prevention with `ToolCallTracker` and `AgentGuardrails` ([#97](https://github.com/glaucia86/repo-doctor/pull/97)) +- **Agent Guardrails**: Loop prevention with `ToolCallTracker` and `AgentGuardrails` ([#97](https://github.com/glaucia86/repocheckai/pull/97)) - Step limit enforcement (30 standard / 40 deep) - Consecutive identical call detection - Sequence loop detection (A→B→A→B patterns) - Progressive response: warn → inject replan message → abort -- **Testing Infrastructure**: 86 unit tests across 7 test files ([#98](https://github.com/glaucia86/repo-doctor/pull/98)) +- **Testing Infrastructure**: 86 unit tests across 7 test files ([#98](https://github.com/glaucia86/repocheckai/pull/98)) - `tests/cli/parsers/repoParser.test.ts` (12 tests) - `tests/cli/parsers/reportExtractor.test.ts` (9 tests) - `tests/cli/state/appState.test.ts` (16 tests) @@ -198,12 +208,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 - `tests/core/agent/eventHandler.test.ts` (17 tests) - `tests/core/agent/toolCallTracker.test.ts` (13 tests) - `tests/core/agent/guardrails.test.ts` (11 tests) -- **Vitest Configuration**: `vitest.config.ts` with proper TypeScript support ([#99](https://github.com/glaucia86/repo-doctor/pull/99)) -- **Deep Analysis Improvements**: Enhanced PHASE 6 instructions with comprehensive checklist ([#100](https://github.com/glaucia86/repo-doctor/pull/100)) +- **Vitest Configuration**: `vitest.config.ts` with proper TypeScript support ([#99](https://github.com/glaucia86/repocheckai/pull/99)) +- **Deep Analysis Improvements**: Enhanced PHASE 6 instructions with comprehensive checklist ([#100](https://github.com/glaucia86/repocheckai/pull/100)) ### Changed -- **Major Refactoring (SOLID Principles)**: ([#101](https://github.com/glaucia86/repo-doctor/pull/101)) +- **Major Refactoring (SOLID Principles)**: ([#101](https://github.com/glaucia86/repocheckai/pull/101)) - `src/cli.ts`: 1165 → 186 lines (-84%) - Extracted `src/cli/chatLoop.ts` — Interactive REPL - Extracted `src/cli/handlers/` — One file per command (SRP) @@ -212,11 +222,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 - Extracted `src/core/agent/prompts/` — Isolated system and analysis prompts (OCP) - Extracted `src/tools/` — Individual tool files (DIP) - Extracted `src/ui/display/` — Modular UI components -- **Interfaces**: Added `src/types/interfaces.ts` with shared interfaces (ISP) ([#102](https://github.com/glaucia86/repo-doctor/pull/102)) +- **Interfaces**: Added `src/types/interfaces.ts` with shared interfaces (ISP) ([#102](https://github.com/glaucia86/repocheckai/pull/102)) ### Fixed -- `/copy` command now captures full report (not just Deep Analysis section) ([#103](https://github.com/glaucia86/repo-doctor/pull/103)) +- `/copy` command now captures full report (not just Deep Analysis section) ([#103](https://github.com/glaucia86/repocheckai/pull/103)) --- @@ -224,31 +234,31 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Breaking Changes -- **CLI Interface**: Removed legacy command-line arguments in favor of interactive chat mode. Use `repo-doctor analyze ` instead of direct CLI arguments ([#89](https://github.com/glaucia86/repo-doctor/pull/89)) -- **Configuration**: Environment variable names changed for better consistency (`GITHUB_TOKEN` now preferred over `GH_TOKEN` for API access) ([#90](https://github.com/glaucia86/repo-doctor/pull/90)) +- **CLI Interface**: Removed legacy command-line arguments in favor of interactive chat mode. Use `repocheck analyze ` instead of direct CLI arguments ([#89](https://github.com/glaucia86/repocheckai/pull/89)) +- **Configuration**: Environment variable names changed for better consistency (`GITHUB_TOKEN` now preferred over `GH_TOKEN` for API access) ([#90](https://github.com/glaucia86/repocheckai/pull/90)) ### Added -- **Deep Analysis Mode**: New `/deep` command with Repomix integration for comprehensive source code analysis ([#85](https://github.com/glaucia86/repo-doctor/pull/85)) -- **Security**: Content sanitization utilities to prevent prompt injection attacks ([#87](https://github.com/glaucia86/repo-doctor/pull/87)) -- **Documentation**: Comprehensive Copilot instructions (`.github/copilot-instructions.md`) ([#88](https://github.com/glaucia86/repo-doctor/pull/88)) -- **Documentation**: AGENTS.md with improved clarity and detail for agent configuration ([#86](https://github.com/glaucia86/repo-doctor/pull/86)) +- **Deep Analysis Mode**: New `/deep` command with Repomix integration for comprehensive source code analysis ([#85](https://github.com/glaucia86/repocheckai/pull/85)) +- **Security**: Content sanitization utilities to prevent prompt injection attacks ([#87](https://github.com/glaucia86/repocheckai/pull/87)) +- **Documentation**: Comprehensive Copilot instructions (`.github/copilot-instructions.md`) ([#88](https://github.com/glaucia86/repocheckai/pull/88)) +- **Documentation**: AGENTS.md with improved clarity and detail for agent configuration ([#86](https://github.com/glaucia86/repocheckai/pull/86)) ### Changed -- Enhanced README with improved structure, clarity, and visual formatting ([#91](https://github.com/glaucia86/repo-doctor/pull/91)) -- Updated demo image for better visual representation ([#92](https://github.com/glaucia86/repo-doctor/pull/92)) -- Reorganized README structure for better project description ([#93](https://github.com/glaucia86/repo-doctor/pull/93)) +- Enhanced README with improved structure, clarity, and visual formatting ([#91](https://github.com/glaucia86/repocheckai/pull/91)) +- Updated demo image for better visual representation ([#92](https://github.com/glaucia86/repocheckai/pull/92)) +- Reorganized README structure for better project description ([#93](https://github.com/glaucia86/repocheckai/pull/93)) ### Fixed -- License section header for improved clarity ([#94](https://github.com/glaucia86/repo-doctor/pull/94)) +- License section header for improved clarity ([#94](https://github.com/glaucia86/repocheckai/pull/94)) ## [1.0.0] - 2026-01-22 ### Added -- Initial release of Repo Doctor +- Initial release of RepoCheckAI - **Core Features**: - CLI with interactive chat mode using Commander.js - GitHub repository analysis via Octokit REST API @@ -282,12 +292,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 --- -[2.4.0]: https://github.com/glaucia86/repo-doctor/compare/v2.3.0...v2.4.0 -[2.3.0]: https://github.com/glaucia86/repo-doctor/compare/v2.2.0...v2.3.0 -[2.2.0]: https://github.com/glaucia86/repo-doctor/compare/v2.1.0...v2.2.0 -[2.1.2]: https://github.com/glaucia86/repo-doctor/compare/v2.1.1...v2.1.2 -[2.1.0]: https://github.com/glaucia86/repo-doctor/compare/v2.0.0...v2.1.0 -[2.0.0]: https://github.com/glaucia86/repo-doctor/compare/v1.0.0...v2.0.0 -[1.0.0]: https://github.com/glaucia86/repo-doctor/releases/tag/v1.0.0 -[2.5.0]: https://github.com/glaucia86/repo-doctor/compare/v2.4.0...v2.5.0 -[Unreleased]: https://github.com/glaucia86/repo-doctor/compare/v2.5.0...HEAD +[2.4.0]: https://github.com/glaucia86/repocheckai/compare/v2.3.0...v2.4.0 +[2.3.0]: https://github.com/glaucia86/repocheckai/compare/v2.2.0...v2.3.0 +[2.2.0]: https://github.com/glaucia86/repocheckai/compare/v2.1.0...v2.2.0 +[2.1.2]: https://github.com/glaucia86/repocheckai/compare/v2.1.1...v2.1.2 +[2.1.0]: https://github.com/glaucia86/repocheckai/compare/v2.0.0...v2.1.0 +[2.0.0]: https://github.com/glaucia86/repocheckai/compare/v1.0.0...v2.0.0 +[1.0.0]: https://github.com/glaucia86/repocheckai/releases/tag/v1.0.0 +[2.5.0]: https://github.com/glaucia86/repocheckai/compare/v2.4.0...v2.5.0 +[Unreleased]: https://github.com/glaucia86/repocheckai/compare/v2.5.0...HEAD + + diff --git a/README.md b/README.md index 891291a..e633774 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,8 @@

- Repo Doctor Banner + RepoCheckAI Banner

-

🩺 Repo Doctor

+

🩺 RepoCheckAI

AI-powered GitHub Repository Health Analyzer
@@ -10,34 +10,34 @@

- - Stars + + Stars - - Forks + + Forks - - CI + + CI - - npm version + + npm version - - Coverage + + Coverage License - - Dependencies + + Dependencies - - Bundle Size + + Bundle Size

- Website • + WebsiteQuick StartFeaturesHow It Works • @@ -49,7 +49,7 @@ ## 📖 Overview -**Repo Doctor** 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. +**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. ### Two Analysis Modes @@ -118,11 +118,11 @@ #### 🚀 Auto-Create Issues for Each Problem Found ```bash -export GITHUB_TOKEN=ghp_xxx # or REPO_DOCTOR_GITHUB_TOKEN, as configured -repo-doctor analyze owner/repo --issue -# Creates: 🔴 [Repo Doctor] docs: Missing README -# 🟠 [Repo Doctor] ci: No CI/CD Pipeline -# 🟡 [Repo Doctor] dx: Code Quality 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 Issues ``` **Each issue includes:** @@ -140,7 +140,7 @@ export GITHUB_TOKEN=ghp_your_token_here gh auth login # Then start interactive mode -repo-doctor chat +repocheck chat /analyze facebook/react --issue /deep microsoft/vscode ``` @@ -154,7 +154,7 @@ repo-doctor chat ## � Quick Start (5 minutes) -Want to see Repo Doctor create GitHub issues automatically? +Want to see RepoCheckAI create GitHub issues automatically? ```bash # 1. Get a GitHub token (see detailed setup below) @@ -162,7 +162,7 @@ Want to see Repo Doctor create GitHub issues automatically? export GITHUB_TOKEN=ghp_your_token_here # 3. Analyze and create issues automatically! -repo-doctor analyze your-username/your-repo --issue +repocheck analyze your-username/your-repo --issue ``` **Result:** Multiple GitHub issues created with detailed analysis, impact assessment, and fix instructions! 🎉 @@ -185,101 +185,31 @@ For the `--issue` feature, you'll need a GitHub Personal Access Token with speci --- -## 🧭 Detailed --issue Setup (and 401 Troubleshooting) +## 🧭 Issue Publishing TL;DR -This section explains, step by step, how to create the right token, avoid 401 errors, and run `--issue` safely. It also clarifies the two authentication paths used by Repo Doctor. +`--issue` (CLI) and `Publish to GitHub Issues` (Web UI) both need GitHub API credentials with issue-write permission. -### 1) Understand the two auth paths +### CLI -- **Copilot SDK auth (models and analysis)** uses GitHub Copilot access. If this fails, you will see: `Failed to list models: 401`. -- **GitHub API auth (repo read + issue creation)** uses your PAT. If this fails, you will see 401/403 when listing files or creating issues. - -### 2) Clean environment (important) - -Do this before testing to avoid old tokens interfering. - -```powershell -Remove-Item Env:GITHUB_TOKEN, Env:GH_TOKEN -ErrorAction SilentlyContinue -``` - -### 3) Authenticate Copilot SDK (fixes "Failed to list models: 401") - -Use GitHub CLI login to get an OAuth token that Copilot accepts. - -```powershell -gh auth logout -gh auth login -``` - -Choose: -- Host: GitHub.com -- Login via web -- Git operations: HTTPS - -Confirm login: - -```powershell -gh auth status -``` - -Export the token for Repo Doctor: - -```powershell -$env:GH_TOKEN = (gh auth token) -``` - -### 4) Create a PAT for `--issue` (GitHub API) - -You have two supported paths. Classic PAT is the most reliable. - -#### Option A: Classic PAT (recommended) - -1. GitHub -> Settings -> Developer settings -> Personal access tokens -> **Tokens (classic)** -2. Click **Generate new token (classic)** -3. Select scopes: - - `repo` (private + public) **or** `public_repo` (public only) -4. Generate and copy the token once - -#### Option B: Fine-grained PAT - -1. GitHub -> Settings -> Developer settings -> Personal access tokens -> **Fine-grained tokens** -2. **Repository access**: - - **All repositories** (if you want to create issues in any repo you own) - - or **Only select repositories** (recommended for least privilege) -3. **Repository permissions** (minimum): - - **Metadata**: Read-only (Required) - - **Contents**: Read-only - - **Issues**: Read and write -4. **Account permissions**: keep **No access** - -### 5) Run Repo Doctor with `--issue` - -Use `GH_TOKEN` for Copilot and pass the PAT only for issue creation. - -```powershell -# Copilot SDK auth (models/analysis) -$env:GH_TOKEN = (gh auth token) - -# Run in dev (chat) and create issues -npm run dev:cli +```bash +export GITHUB_TOKEN=ghp_your_pat_here +repocheck analyze owner/repo --issue ``` -In the app: +### Web UI +```bash +npm run dev:local-ui ``` -/deep owner/repo --issue --token -``` - -### 6) Quick diagnosis checklist -- **401 on models**: Copilot auth failed -> redo Step 3 (gh auth + GH_TOKEN) -- **401/403 on issue creation**: PAT lacks access or `Issues: Read/Write` -- **Public repo but want issues**: PAT still needs `Issues: Read/Write` -- **Org repo**: your account must have permission to create issues in that repo +In the form: +1. Enable `Publish to GitHub Issues` +2. Optional: paste `GitHub Token` (overrides server env token) +3. Run analysis ---- +If no token is provided in the field, the backend uses `GITHUB_TOKEN` from the server environment. -For the complete step-by-step guide (including PAT creation screens and diagnostics), see [docs/issue-publishing.md](docs/issue-publishing.md). +For full step-by-step setup and 401/403 troubleshooting, see [docs/issue-publishing.md](docs/issue-publishing.md). --- @@ -306,8 +236,8 @@ For the complete step-by-step guide (including PAT creation screens and diagnost ```bash # Clone the repository -git clone https://github.com/glaucia86/repo-doctor.git -cd repo-doctor +git clone https://github.com/glaucia86/repocheckai.git +cd repocheckai # Install dependencies and build npm install @@ -321,16 +251,16 @@ npm link ```bash # Interactive mode -repo-doctor +repocheck # Direct analysis -repo-doctor vercel/next.js +repocheck vercel/next.js # Deep analysis with premium model -repo-doctor vercel/next.js --model claude-sonnet-4 --deep +repocheck vercel/next.js --model claude-sonnet-4 --deep # 🚀 Auto-create GitHub issues for each problem found -repo-doctor vercel/next.js --issue +repocheck vercel/next.js --issue ``` > [!NOTE] @@ -354,7 +284,7 @@ repo-doctor vercel/next.js --issue | `/export [path]` | Save report as markdown file | | `/model [name]` | Switch AI model (now works in onboarding phase) | | `/help` | Show all available commands | -| `/quit` | Exit Repo Doctor | +| `/quit` | Exit RepoCheckAI | > [!TIP] > Use `/deep` for comprehensive code quality analysis. Use `/analyze` for quick governance checks. @@ -402,27 +332,27 @@ Current MVP capabilities: ### Quick Analysis ```bash -repo-doctor +repocheck /analyze microsoft/vscode ``` ### Deep Analysis with Custom Model ```bash -repo-doctor +repocheck /model claude-sonnet-4 /deep facebook/react ``` ### Export Report ```bash -repo-doctor +repocheck /analyze vercel/next.js /export nextjs-report.md ``` ### Interactive Mode ```bash -repo-doctor +repocheck # Then use commands interactively /analyze myorg/myrepo /copy @@ -458,7 +388,7 @@ repo-doctor | [🏗️ Architecture](docs/architecture.md) | Technical architecture and design | | [❓ FAQ](docs/faq.md) | Frequently asked questions | | [🔧 Troubleshooting](docs/troubleshooting.md) | Common issues and solutions | -| [🤝 Contributing](docs/CONTRIBUTING.md) | How to contribute to Repo Doctor | +| [🤝 Contributing](docs/CONTRIBUTING.md) | How to contribute to RepoCheckAI | > 📖 **Full documentation:** [docs/index.md](docs/index.md) @@ -532,7 +462,7 @@ src/ ## ⭐ Support This Project -If you find Repo Doctor useful: +If you find RepoCheckAI useful: @@ -546,11 +476,11 @@ If you find Repo Doctor useful:

- - Issues + + Issues - - Pull Requests + + Pull Requests

@@ -558,11 +488,11 @@ If you find Repo Doctor useful: ## 📈 Star History - + - - - Star History Chart + + + Star History Chart @@ -601,5 +531,8 @@ MIT © [Glaucia Lemos](https://github.com/glaucia86)

- ⬆️ Back to Top + ⬆️ Back to Top

+ + + diff --git a/SECURITY.md b/SECURITY.md index eeba75b..accdb81 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -9,7 +9,7 @@ ## Reporting a Vulnerability -If you discover a security vulnerability in Repo Doctor, please report it responsibly: +If you discover a security vulnerability in Repo Check AI, please report it responsibly: 1. Do NOT open a public GitHub issue 2. Email: skinclear86@gmail.com with details @@ -25,8 +25,9 @@ We will acknowledge your report and work with you to address the issue promptly. ## Security Best Practices -Repo Doctor is designed with security in mind: +Repo Check AI is designed with security in mind: - File content is treated as data (not instructions) - GitHub tokens are handled securely - No data storage - analysis runs locally - Content sanitization for prompt injection protection + diff --git a/docs/AI-MODELS.md b/docs/AI-MODELS.md index 820a2dd..6ac61e8 100644 --- a/docs/AI-MODELS.md +++ b/docs/AI-MODELS.md @@ -1,6 +1,6 @@ # 🤖 Available AI Models -Repo Doctor supports multiple AI models through the GitHub Copilot SDK. Choose the model that best fits your needs and subscription level. +RepoCheckAI supports multiple AI models through the GitHub Copilot SDK. Choose the model that best fits your needs and subscription level. --- @@ -28,7 +28,7 @@ Available to all GitHub Copilot users (Individual, Business, Enterprise): ### GPT-4o ```bash -repo-doctor vercel/next.js --model gpt-4o +repocheck vercel/next.js --model gpt-4o ``` - **Best for:** Quick health checks, daily use - **Speed:** Fast @@ -36,7 +36,7 @@ repo-doctor vercel/next.js --model gpt-4o ### GPT-4.1 ```bash -repo-doctor vercel/next.js --model gpt-4.1 +repocheck vercel/next.js --model gpt-4.1 ``` - **Best for:** General purpose analysis - **Speed:** Fast @@ -44,7 +44,7 @@ repo-doctor vercel/next.js --model gpt-4.1 ### GPT-5 Mini ```bash -repo-doctor vercel/next.js --model gpt-5-mini +repocheck vercel/next.js --model gpt-5-mini ``` - **Best for:** Lightweight tasks, simple repositories - **Speed:** Very fast @@ -58,7 +58,7 @@ Require GitHub Copilot Pro, Business, or Enterprise subscription: ### Claude Sonnet 4 (Default) ```bash -repo-doctor vercel/next.js --model claude-sonnet-4 +repocheck vercel/next.js --model claude-sonnet-4 ``` - **Best for:** Balanced analysis, recommended default - **Speed:** Moderate @@ -66,7 +66,7 @@ repo-doctor vercel/next.js --model claude-sonnet-4 ### Claude Sonnet 4.5 ```bash -repo-doctor vercel/next.js --model claude-sonnet-4.5 +repocheck vercel/next.js --model claude-sonnet-4.5 ``` - **Best for:** Enhanced reasoning tasks - **Speed:** Moderate @@ -74,7 +74,7 @@ repo-doctor vercel/next.js --model claude-sonnet-4.5 ### Claude Opus 4.5 ```bash -repo-doctor vercel/next.js --model claude-opus-4.5 +repocheck vercel/next.js --model claude-opus-4.5 ``` - **Best for:** Complex repositories, deep analysis - **Speed:** Slower (3x rate limit cost) @@ -82,7 +82,7 @@ repo-doctor vercel/next.js --model claude-opus-4.5 ### GPT-5 ```bash -repo-doctor vercel/next.js --model gpt-5 +repocheck vercel/next.js --model gpt-5 ``` - **Best for:** Advanced analysis - **Speed:** Moderate @@ -90,7 +90,7 @@ repo-doctor vercel/next.js --model gpt-5 ### GPT-5.1 Codex ```bash -repo-doctor vercel/next.js --model gpt-5.1-codex +repocheck vercel/next.js --model gpt-5.1-codex ``` - **Best for:** Code-heavy repositories - **Speed:** Moderate @@ -98,7 +98,7 @@ repo-doctor vercel/next.js --model gpt-5.1-codex ### GPT-5.2 Codex ```bash -repo-doctor vercel/next.js --model gpt-5.2-codex +repocheck vercel/next.js --model gpt-5.2-codex ``` - **Best for:** Latest code analysis capabilities - **Speed:** Moderate @@ -106,7 +106,7 @@ repo-doctor vercel/next.js --model gpt-5.2-codex ### GPT-5.3 Codex ```bash -repo-doctor vercel/next.js --model gpt-5.3-codex +repocheck vercel/next.js --model gpt-5.3-codex ``` - **Best for:** Advanced coding tasks and complex codebases - **Speed:** Moderate @@ -114,7 +114,7 @@ repo-doctor vercel/next.js --model gpt-5.3-codex ### O3 ```bash -repo-doctor vercel/next.js --model o3 +repocheck vercel/next.js --model o3 ``` - **Best for:** Complex reasoning, large repositories - **Speed:** Slower @@ -138,7 +138,7 @@ Use the `/model` command to switch models interactively: Specify the model when starting: ```bash -repo-doctor owner/repo --model gpt-4o +repocheck owner/repo --model gpt-4o ``` ### Interactive Selection @@ -216,3 +216,5 @@ export GH_TOKEN="$(gh auth token)" ``` See [issue-publishing.md](issue-publishing.md) for full steps. + + diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index 1c56c8b..f2fb7dc 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -1,6 +1,6 @@ -# 🤝 Contributing to Repo Doctor +# 🤝 Contributing to RepoCheckAI -Thank you for your interest in contributing to Repo Doctor! This document provides guidelines and instructions for contributing. +Thank you for your interest in contributing to RepoCheckAI! This document provides guidelines and instructions for contributing. --- @@ -27,12 +27,12 @@ By participating in this project, you agree to maintain a respectful and inclusi 1. **Fork** the repository on GitHub 2. **Clone** your fork locally: ```bash - git clone https://github.com/YOUR_USERNAME/repo-doctor.git - cd repo-doctor + git clone https://github.com/YOUR_USERNAME/repocheckai.git + cd repocheckai ``` 3. **Add upstream** remote: ```bash - git remote add upstream https://github.com/glaucia86/repo-doctor.git + git remote add upstream https://github.com/glaucia86/repocheckai.git ``` --- @@ -83,7 +83,7 @@ npm run test:integration ## Project Structure ``` -repo-doctor/ +repocheck/ ├── site/ # Static website (GitHub Pages) ├── src/ │ ├── index.ts # Package entrypoint @@ -148,7 +148,7 @@ chore: update dependencies 2. **Make your changes** and test locally: ```bash npm run build - repo-doctor # Test your changes + repocheck # Test your changes ``` 3. **Commit** your changes: @@ -218,10 +218,12 @@ chore: update dependencies ## Need Help? -- 💬 Open a [Discussion](https://github.com/glaucia86/repo-doctor/discussions) -- 🐛 Report a [Bug](https://github.com/glaucia86/repo-doctor/issues/new?template=bug_report.md) -- 💡 Request a [Feature](https://github.com/glaucia86/repo-doctor/issues/new?template=feature_request.md) +- 💬 Open a [Discussion](https://github.com/glaucia86/repocheckai/discussions) +- 🐛 Report a [Bug](https://github.com/glaucia86/repocheckai/issues/new?template=bug_report.md) +- 💡 Request a [Feature](https://github.com/glaucia86/repocheckai/issues/new?template=feature_request.md) --- Thank you for contributing! 💚 + + diff --git a/docs/GUIDE.md b/docs/GUIDE.md index d3301cb..780d0e1 100644 --- a/docs/GUIDE.md +++ b/docs/GUIDE.md @@ -1,6 +1,6 @@ -# 📖 Repo Doctor User Guide +# 📖 RepoCheckAI User Guide -Complete guide for using Repo Doctor CLI. +Complete guide for using RepoCheckAI CLI. --- @@ -21,28 +21,28 @@ Complete guide for using Repo Doctor CLI. ```bash # Start interactive mode - will prompt for repository and model -repo-doctor +repocheck # Analyze a specific repository directly -repo-doctor vercel/next.js +repocheck vercel/next.js # Analyze with a specific model -repo-doctor vercel/next.js --model gpt-4o +repocheck vercel/next.js --model gpt-4o ``` --- ## Interactive Chat Mode -When you run `repo-doctor`, you enter an interactive chat interface: +When you run `repocheck`, you enter an interactive chat interface: ``` ╭─────────────────────────────────────────╮ -│ 🩺 REPO DOCTOR v2.0 │ +│ 🩺 REPO CHECK AI v2.0 │ │ GitHub Repository Health Analyzer │ ╰─────────────────────────────────────────╯ - ✨ Welcome to Repo Doctor! + ✨ Welcome to RepoCheckAI! Enter repository (owner/repo): vercel/next.js @@ -73,7 +73,7 @@ After analysis, you'll see options to copy, export, or analyze another repositor | `/model [name]` | Switch AI model | `/model gpt-4o` | | `/clear` | Clear the screen | `/clear` | | `/help` | Show available commands | `/help` | -| `/quit` | Exit Repo Doctor | `/quit` | +| `/quit` | Exit RepoCheckAI | `/quit` | > 💡 **Tip:** Use `/deep` for comprehensive analysis of complex repositories. It reads all source files and provides more detailed evidence. @@ -132,7 +132,7 @@ The `/deep` command uses [Repomix](https://github.com/yamadashy/repomix) to perf The `/export` command supports flexible paths: ```bash -# Save to default location: ~/repo-doctor/reports/ +# Save to default location: ~/repocheck/reports/ /export # Save to Desktop @@ -155,7 +155,7 @@ Reports are saved with UTF-8 encoding (with BOM) to preserve emojis correctly. ## Command Line Options ```bash -repo-doctor [repository] [options] +repocheck [repository] [options] Options: --token GitHub token for private repos (or set GITHUB_TOKEN env) @@ -172,20 +172,20 @@ Options: ```bash # Analyze a public repository -repo-doctor microsoft/typescript +repocheck microsoft/typescript # Analyze with full URL -repo-doctor https://github.com/facebook/react +repocheck https://github.com/facebook/react # Analyze a private repository export GITHUB_TOKEN=ghp_xxxxx -repo-doctor owner/private-repo +repocheck owner/private-repo # Use a free model -repo-doctor vercel/next.js --model gpt-4o +repocheck vercel/next.js --model gpt-4o # Auto-export after analysis -repo-doctor vercel/next.js --export +repocheck vercel/next.js --export ``` --- @@ -201,13 +201,13 @@ To analyze private repositories, you need to provide a GitHub Personal Access To export GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxx # Now analyze any private repo -repo-doctor my-org/private-repo +repocheck my-org/private-repo ``` ### Option 2: Command Line Argument ```bash -repo-doctor my-org/private-repo --token ghp_xxxxxxxxxxxxxxxxxxxx +repocheck my-org/private-repo --token ghp_xxxxxxxxxxxxxxxxxxxx ``` ### Creating a GitHub Token @@ -225,6 +225,8 @@ repo-doctor my-org/private-repo --token ghp_xxxxxxxxxxxxxxxxxxxx Use `--issue` to create GitHub issues with the analysis output. This requires a PAT with issue write access and Copilot SDK auth for model access. +Web UI equivalent: run `npm run dev:local-ui` and enable `Publish to GitHub Issues` in the form. + > **Tip:** If you plan to use `--issue`, the best model for report quality is **Claude Sonnet 4.5**. ```bash @@ -232,7 +234,7 @@ Use `--issue` to create GitHub issues with the analysis output. This requires a export GH_TOKEN="$(gh auth token)" # Create issues during analysis -repo-doctor analyze owner/repo --issue --token ghp_your_pat_here +repocheck analyze owner/repo --issue --token ghp_your_pat_here ``` For a full step-by-step guide and 401 troubleshooting, see [issue-publishing.md](issue-publishing.md). @@ -241,7 +243,7 @@ For a full step-by-step guide and 401 troubleshooting, see [issue-publishing.md] ## Priority Levels -Repo Doctor classifies findings into three priority levels: +RepoCheckAI classifies findings into three priority levels: | Priority | Meaning | Examples | |----------|---------|----------| @@ -297,11 +299,11 @@ jobs: node-version: '20' cache: 'npm' - - name: Install Repo Doctor - run: npm install -g repo-doctor + - name: Install RepoCheckAI + run: npm install -g repocheck - name: Run health analysis - run: repo-doctor analyze ${{ github.repository }} --export health-report.md + run: repocheck analyze ${{ github.repository }} --export health-report.md env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} @@ -342,11 +344,11 @@ pipeline { stage('Repository Health Check') { steps { script { - // Install Repo Doctor if not available globally - sh 'npm install -g repo-doctor' + // Install RepoCheckAI if not available globally + sh 'npm install -g repocheck' // Run analysis - sh "repo-doctor analyze ${env.GIT_URL.replace('.git', '').split('/').slice(-2).join('/')} --export health-report.md" + sh "repocheck analyze ${env.GIT_URL.replace('.git', '').split('/').slice(-2).join('/')} --export health-report.md" // Archive report archiveArtifacts artifacts: 'health-report.md', fingerprint: true @@ -400,12 +402,12 @@ jobs: steps: - checkout - run: - name: Install Repo Doctor - command: npm install -g repo-doctor + name: Install RepoCheckAI + command: npm install -g repocheck - run: name: Run Health Analysis command: | - repo-doctor analyze $CIRCLE_PROJECT_USERNAME/$CIRCLE_PROJECT_REPONAME --export health-report.md + repocheck analyze $CIRCLE_PROJECT_USERNAME/$CIRCLE_PROJECT_REPONAME --export health-report.md environment: GITHUB_TOKEN: $GITHUB_TOKEN - store_artifacts: @@ -441,7 +443,7 @@ DATE=$(date +%Y-%m-%d) mkdir -p "$OUTPUT_DIR" # Run analysis -repo-doctor analyze "$REPO" --export "$OUTPUT_DIR/health-report-$DATE.md" +repocheck analyze "$REPO" --export "$OUTPUT_DIR/health-report-$DATE.md" # Generate summary SCORE=$(grep "Health Score:" "$OUTPUT_DIR/health-report-$DATE.md" | grep -o "[0-9]\+") @@ -467,7 +469,7 @@ REPO="your-org/your-repo" SLACK_WEBHOOK_URL="https://hooks.slack.com/services/YOUR/WEBHOOK/URL" # Run analysis -repo-doctor analyze "$REPO" --export health-report.md +repocheck analyze "$REPO" --export health-report.md # Extract key metrics SCORE=$(grep "Health Score:" health-report.md | grep -o "[0-9]\+") @@ -541,7 +543,7 @@ export GITHUB_TOKEN="your-github-token" export GH_TOKEN="$(gh auth token)" # Create issues for all findings -repo-doctor analyze "$REPO" --issue +repocheck analyze "$REPO" --issue # Or create issues only for critical (P0) findings # (This would require custom scripting to filter the report) @@ -568,7 +570,7 @@ mkdir -p "$OUTPUT_DIR" for repo in "${REPOS[@]}"; do echo "Analyzing $repo..." - repo-doctor analyze "$repo" --export "$OUTPUT_DIR/$(basename "$repo").md" + repocheck analyze "$repo" --export "$OUTPUT_DIR/$(basename "$repo").md" done # Generate summary report @@ -595,7 +597,7 @@ REPO="your-org/your-repo" HISTORY_FILE="./health-history.csv" # Run analysis -repo-doctor analyze "$REPO" --export temp-report.md +repocheck analyze "$REPO" --export temp-report.md # Extract metrics DATE=$(date +%Y-%m-%d) @@ -624,7 +626,7 @@ Add repository health checks to your pre-commit workflow: # .git/hooks/pre-commit # Run quick health check -repo-doctor analyze "$(git config --get remote.origin.url | sed 's/.*github.com[:/]\(.*\)\.git/\1/')" --export /tmp/health-check.md +repocheck analyze "$(git config --get remote.origin.url | sed 's/.*github.com[:/]\(.*\)\.git/\1/')" --export /tmp/health-check.md SCORE=$(grep "Health Score:" /tmp/health-check.md | grep -o "[0-9]\+") @@ -647,9 +649,9 @@ Create a VS Code task for easy access: "version": "2.0.0", "tasks": [ { - "label": "Run Repo Doctor", + "label": "Run RepoCheckAI", "type": "shell", - "command": "repo-doctor", + "command": "repocheck", "group": "build", "presentation": { "echo": true, @@ -661,9 +663,12 @@ Create a VS Code task for easy access: { "label": "Analyze Current Repo", "type": "shell", - "command": "repo-doctor analyze $(git config --get remote.origin.url | sed 's/.*github.com[:/]\(.*\)\.git/\\1/')", + "command": "repocheck analyze $(git config --get remote.origin.url | sed 's/.*github.com[:/]\(.*\)\.git/\\1/')", "group": "build" } ] } ``` + + + diff --git a/docs/ai/PROMPTS.md b/docs/ai/PROMPTS.md index 0aa6fe6..e9659ac 100644 --- a/docs/ai/PROMPTS.md +++ b/docs/ai/PROMPTS.md @@ -1,4 +1,4 @@ -# Prompt System — Repo Doctor +# Prompt System — Repo Check AI ## Architecture @@ -104,3 +104,4 @@ const CATEGORY_WEIGHTS = { ### ⚠️ P1 — High Priority ### 💡 P2 — Suggestions ``` + diff --git a/docs/ai/SECURITY.md b/docs/ai/SECURITY.md index b59fadf..5d7be3e 100644 --- a/docs/ai/SECURITY.md +++ b/docs/ai/SECURITY.md @@ -1,4 +1,4 @@ -# Security — Repo Doctor +# Security — Repo Check AI ## Content Sanitization @@ -68,3 +68,4 @@ const patterns = [ ## Implementation See `src/utils/sanitizer.ts` for full implementation. + diff --git a/docs/ai/SESSION.md b/docs/ai/SESSION.md index 275f841..3756186 100644 --- a/docs/ai/SESSION.md +++ b/docs/ai/SESSION.md @@ -1,4 +1,4 @@ -# Session Configuration — Repo Doctor +# Session Configuration — Repo Check AI ## Initialization @@ -82,3 +82,4 @@ session.on((event: SessionEvent) => { | Sequence Loop | A→B→A→B | Warn → Abort | Config in `src/application/core/agent/guardrails.ts`. + diff --git a/docs/ai/TESTING.md b/docs/ai/TESTING.md index 8c6af00..a719faf 100644 --- a/docs/ai/TESTING.md +++ b/docs/ai/TESTING.md @@ -1,4 +1,4 @@ -# Testing — Repo Doctor +# Testing — Repo Check AI ## Commands @@ -53,3 +53,4 @@ npm run dev:cli -- /deep owner/repo # Deep analysis - **Non-standard structures**: No src/, custom layouts - **Binary repos**: Mostly images/assets - **Forked repos**: Fork metadata handling + diff --git a/docs/ai/TOOLS.md b/docs/ai/TOOLS.md index 1c5bb04..0bf0b7e 100644 --- a/docs/ai/TOOLS.md +++ b/docs/ai/TOOLS.md @@ -1,4 +1,4 @@ -# Custom Tools — Repo Doctor +# Custom Tools — Repo Check AI ## Tool: get_repo_meta @@ -127,3 +127,4 @@ README.md, LICENSE, CONTRIBUTING.md, package.json, .github/** | 404 | `{ found: false }` | Use as evidence | | 403 | Rate limit error | Show warning, partial report | | Timeout | Operation timeout | Partial results | + diff --git a/docs/analysis-categories.md b/docs/analysis-categories.md index 07c626a..0f2a5b8 100644 --- a/docs/analysis-categories.md +++ b/docs/analysis-categories.md @@ -1,6 +1,6 @@ # 📊 Analysis Categories -Repo Doctor evaluates repositories across six critical categories. This document details what gets analyzed in each category and how findings are classified. +Repo Check AI evaluates repositories across six critical categories. This document details what gets analyzed in each category and how findings are classified. --- @@ -108,7 +108,7 @@ Each category starts at 100% and deductions are made for missing elements: ### Stack Detection -Repo Doctor automatically detects the project stack: +Repo Check AI automatically detects the project stack: | Stack | Detection Files | |-------|-----------------| @@ -435,3 +435,4 @@ overall_score = (

← Back to Documentation

+ diff --git a/docs/announcements/repocheckai-migration.md b/docs/announcements/repocheckai-migration.md new file mode 100644 index 0000000..ee3020b --- /dev/null +++ b/docs/announcements/repocheckai-migration.md @@ -0,0 +1,50 @@ +# RepoCheckAI Migration Announcement + +Date: 2026-02-17 + +## Summary + +`Repo Check AI` is now `RepoCheckAI`. + +- Official npm package: `repocheckai` +- Official CLI command: `repocheck` +- Legacy command in transition: `repodoctor` + +## Why We Changed + +The new identity aligns product name, package name, and command conventions while keeping continuity for existing users. + +## Command Transition Policy + +- Effective release: `2.5.0` +- Legacy support window: `2` releases +- Legacy support until: `2.6.x` + +During transition: + +- `repocheck` is the default and recommended command. +- `repodoctor` still runs, but shows a deprecation warning. + +After transition: + +- `repodoctor` will be rejected with migration guidance. + +## What You Need To Do + +1. Update scripts and docs to use `repocheck`. +2. Ensure installation references `npm i -g repocheckai`. +3. Remove hard dependencies on `repodoctor` before the end of the transition window. + +## Migration Examples + +```bash +# install +npm i -g repocheckai + +# old (transition only) +repodoctor analyze owner/repo + +# new (recommended) +repocheck analyze owner/repo +``` + diff --git a/docs/architecture.md b/docs/architecture.md index 81b6a53..4ee8e76 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -1,6 +1,6 @@ # 🏗️ Architecture -Technical overview of Repo Doctor's architecture and design decisions. +Technical overview of Repo Check AI's architecture and design decisions. --- @@ -19,11 +19,11 @@ Technical overview of Repo Doctor's architecture and design decisions. ## System Overview -Repo Doctor is built as an **agentic CLI tool** using the GitHub Copilot SDK. It leverages AI to analyze GitHub repositories and provide health assessments. +Repo Check AI is built as an **agentic CLI tool** using the GitHub Copilot SDK. It leverages AI to analyze GitHub repositories and provide health assessments. ```mermaid flowchart TB - subgraph RD["🩺 REPO DOCTOR"] + subgraph RD["🩺 REPO CHECK AI"] direction TB subgraph Input["📥 Input Layer"] @@ -92,7 +92,7 @@ graph LR ## Project Structure ``` -repo-doctor/ +repocheckai/ ├── site/ # Static website (GitHub Pages) │ ├── src/ @@ -252,7 +252,7 @@ export function createOctokit(token?: string): Octokit { return new Octokit({ auth: resolvedToken, - userAgent: "repo-doctor", + userAgent: "repocheckai", }); } ``` @@ -585,7 +585,7 @@ function sanitizeFilePath(path: string): string | null { - Environment variables are preferred - GitHub CLI integration for secure auth -Repo Doctor uses two auth paths: +Repo Check AI uses two auth paths: - Copilot SDK auth via GitHub CLI OAuth token (exported as `GH_TOKEN`) - GitHub API auth for repo access and `--issue` via PAT (`GITHUB_TOKEN` or `--token`) @@ -669,3 +669,4 @@ export const colors = {

← Back to Documentation

+ diff --git a/docs/commands.md b/docs/commands.md index 81f7635..5f535a4 100644 --- a/docs/commands.md +++ b/docs/commands.md @@ -1,6 +1,8 @@ # 💻 Commands Reference -Complete reference for all Repo Doctor CLI commands and options. +Complete reference for all RepoCheckAI CLI commands and options. + +> Transition note: `repocheck` is the official command. `repodoctor` is still accepted temporarily with a deprecation warning. --- @@ -17,7 +19,7 @@ Complete reference for all Repo Doctor CLI commands and options. ## Interactive Commands -When running Repo Doctor in interactive mode, these slash commands are available: +When running RepoCheckAI in interactive mode, these slash commands are available: ### Analysis Commands @@ -70,7 +72,7 @@ When running Repo Doctor in interactive mode, these slash commands are available | `/model` | `[name]` | Switch or display current AI model | | `/clear` | — | Clear the terminal screen | | `/help` | — | Show available commands | -| `/quit` | — | Exit Repo Doctor | +| `/quit` | — | Exit RepoCheckAI | **Examples:** @@ -92,7 +94,7 @@ When running Repo Doctor in interactive mode, these slash commands are available ### Basic Syntax ```bash -repo-doctor [repository] [options] +repocheck [repository] [options] ``` ### Arguments @@ -101,7 +103,7 @@ repo-doctor [repository] [options] |----------|----------|-------------| | `repository` | No | Repository to analyze (owner/repo or URL) | -If no repository is provided, Repo Doctor starts in interactive mode. +If no repository is provided, RepoCheckAI starts in interactive mode. ### Options @@ -119,6 +121,9 @@ If no repository is provided, Repo Doctor starts in interactive mode. | `--version` | `-v` | — | — | Show version number | > **Tip:** If you plan to use `--issue`, the best model for report quality is **Claude Sonnet 4.5**. +> +> **Web UI equivalent:** enable `Publish to GitHub Issues` in the local Web UI form. +> For token/auth setup and `401/403` troubleshooting, see [issue-publishing.md](issue-publishing.md). --- @@ -239,7 +244,7 @@ Exports the report to a file. | Argument | Required | Default | Description | |----------|----------|---------|-------------| -| `path` | No | `~/repo-doctor/reports/` | Output path | +| `path` | No | `~/repocheck/reports/` | Output path | | `format` | No | `md` | Output format (`md` or `json`) | **Examples:** @@ -247,7 +252,7 @@ Exports the report to a file. ```bash # Default location and format /export -# Saves to: ~/repo-doctor/reports/vercel-next.js-2024-01-15.md +# Saves to: ~/repocheck/reports/vercel-next.js-2024-01-15.md # Custom path /export ~/Desktop @@ -380,7 +385,7 @@ Shows all available commands. ### /quit -Exits Repo Doctor. +Exits RepoCheckAI. ```bash /quit @@ -392,15 +397,15 @@ Also accepts: `/exit`, `/q`, `Ctrl+C` ## Environment Variables -Configure Repo Doctor behavior using environment variables: +Configure RepoCheckAI behavior using environment variables: | Variable | Description | Example | |----------|-------------|---------| | `GITHUB_TOKEN` | GitHub personal access token | `ghp_xxxx` | | `GH_TOKEN` | GitHub CLI OAuth token for Copilot SDK | `gho_xxxx` | -| `REPO_DOCTOR_MODEL` | Default AI model | `gpt-4o` | -| `REPO_DOCTOR_TIMEOUT` | Analysis timeout (ms) | `180000` | -| `REPO_DOCTOR_EXPORT_PATH` | Default export path | `~/reports` | +| `REPOCHECKAI_MODEL` | Default AI model | `gpt-4o` | +| `REPOCHECKAI_TIMEOUT` | Analysis timeout (ms) | `180000` | +| `REPOCHECKAI_EXPORT_PATH` | Default export path | `~/reports` | **Example usage:** @@ -408,10 +413,10 @@ Configure Repo Doctor behavior using environment variables: # Set in .bashrc or .zshrc export GITHUB_TOKEN=ghp_xxxxxxxxxxxx export GH_TOKEN="$(gh auth token)" -export REPO_DOCTOR_MODEL=gpt-4o +export REPOCHECKAI_MODEL=gpt-4o # Or inline -GITHUB_TOKEN=ghp_xxxx repo-doctor owner/repo +GITHUB_TOKEN=ghp_xxxx repocheck owner/repo ``` --- @@ -422,19 +427,19 @@ GITHUB_TOKEN=ghp_xxxx repo-doctor owner/repo ```bash # Quick health check -repo-doctor vercel/next.js +repocheck vercel/next.js # Deep audit with premium model -repo-doctor facebook/react --model claude-opus-4.5 --deep +repocheck facebook/react --model claude-opus-4.5 --deep # Analyze and auto-export -repo-doctor microsoft/typescript --export +repocheck microsoft/typescript --export # Private repository -GITHUB_TOKEN=ghp_xxxx repo-doctor my-org/private-repo +GITHUB_TOKEN=ghp_xxxx repocheck my-org/private-repo # With extended timeout for large repos -repo-doctor kubernetes/kubernetes --timeout 300000 +repocheck kubernetes/kubernetes --timeout 300000 ``` ### Batch Analysis @@ -442,7 +447,7 @@ repo-doctor kubernetes/kubernetes --timeout 300000 ```bash # Analyze multiple repos (bash script) for repo in "org/repo1" "org/repo2" "org/repo3"; do - repo-doctor "$repo" --export + repocheck "$repo" --export done ``` @@ -451,3 +456,7 @@ done

← Back to Documentation

+ + + + diff --git a/docs/faq.md b/docs/faq.md index 80f5c38..69dc0bd 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -1,6 +1,6 @@ # ❓ Frequently Asked Questions -Common questions about using Repo Doctor. +Common questions about using RepoCheckAI. --- @@ -17,15 +17,15 @@ Common questions about using Repo Doctor. ## General Questions -### What is Repo Doctor? +### What is RepoCheckAI? -Repo Doctor is an AI-powered CLI tool that analyzes GitHub repositories for health issues. It checks documentation, developer experience, CI/CD, testing, governance, and security practices, then provides a detailed report with prioritized findings and actionable recommendations. +RepoCheckAI is an AI-powered CLI tool that analyzes GitHub repositories for health issues. It checks documentation, developer experience, CI/CD, testing, governance, and security practices, then provides a detailed report with prioritized findings and actionable recommendations. ### How is it different from other code analysis tools? Unlike traditional linters or static analysis tools that focus on code syntax: -| Aspect | Traditional Tools | Repo Doctor | +| Aspect | Traditional Tools | RepoCheckAI | |--------|------------------|-------------| | Focus | Code syntax/style | Project health & best practices | | Scope | Single language | Any language/framework | @@ -35,7 +35,7 @@ Unlike traditional linters or static analysis tools that focus on code syntax: ### What languages/frameworks does it support? -Repo Doctor supports **all languages and frameworks**. It automatically detects your stack and adapts its analysis: +RepoCheckAI supports **all languages and frameworks**. It automatically detects your stack and adapts its analysis: - **JavaScript/TypeScript** (Node.js, React, Vue, etc.) - **Python** (Django, Flask, FastAPI, etc.) @@ -69,7 +69,7 @@ Your code is processed through the GitHub Copilot API, which has enterprise-grad ### Why do I need GitHub Copilot? -Repo Doctor uses the [GitHub Copilot SDK](https://github.com/github/copilot-sdk) for AI capabilities. This SDK requires an active GitHub Copilot subscription. +RepoCheckAI uses the [GitHub Copilot SDK](https://github.com/github/copilot-sdk) for AI capabilities. This SDK requires an active GitHub Copilot subscription. **Subscription options:** - GitHub Copilot Individual ($10/month) @@ -118,7 +118,7 @@ See [Troubleshooting](troubleshooting.md) for more solutions. **Use `/analyze`** for quick health checks and governance reviews. **Use `/deep`** for detailed audits and code quality analysis. -### What files does Repo Doctor read? +### What files does RepoCheckAI read? **Quick analysis (`/analyze`) reads:** - `README.md` @@ -198,7 +198,7 @@ Yes! Switch models anytime: ```bash # Via command line -repo-doctor owner/repo --model gpt-4o +repocheck owner/repo --model gpt-4o # In interactive mode /model claude-sonnet-4 @@ -225,13 +225,13 @@ Yes! You need to provide a GitHub token with `repo` scope: ```bash # Option 1: Environment variable export GITHUB_TOKEN=ghp_xxxxxxxxxxxx -repo-doctor my-org/private-repo +repocheck my-org/private-repo # Option 2: Command line -repo-doctor my-org/private-repo --token ghp_xxxxxxxxxxxx +repocheck my-org/private-repo --token ghp_xxxxxxxxxxxx # Option 3: GitHub CLI (if authenticated) -gh auth login # Then Repo Doctor auto-detects +gh auth login # Then RepoCheckAI auto-detects ``` ### What token scopes are required? @@ -275,6 +275,7 @@ See [issue-publishing.md](issue-publishing.md) for the full step-by-step guide. ### Why does `--issue` return 401/403? Your PAT lacks write access to issues or does not have repo access. +The same rule applies to Web UI publishing (`Publish to GitHub Issues`). - Classic PAT: ensure `repo` (or `public_repo`) is selected - Fine-grained PAT: ensure **Metadata (read)**, **Contents (read)**, **Issues (read/write)** @@ -284,9 +285,9 @@ Your PAT lacks write access to issues or does not have repo access. ## Pricing & Limits -### Is Repo Doctor free? +### Is RepoCheckAI free? -Repo Doctor is **open source and free**. However, it requires: +RepoCheckAI is **open source and free**. However, it requires: - **GitHub Copilot subscription** (paid) - **GitHub API access** (free with limits) @@ -311,7 +312,7 @@ You'll see an error like "Rate limit exceeded". Solutions: ### Are there costs for AI usage? -AI usage is included in your GitHub Copilot subscription. There are no additional charges from Repo Doctor. +AI usage is included in your GitHub Copilot subscription. There are no additional charges from RepoCheckAI. **Note:** Premium models like `claude-opus-4.5` consume rate limits faster (3x cost), which may affect your Copilot usage for other tools. @@ -319,8 +320,8 @@ AI usage is included in your GitHub Copilot subscription. There are no additiona ## More Questions? -- 💬 [Start a Discussion](https://github.com/glaucia86/repo-doctor/discussions) -- 🐛 [Report an Issue](https://github.com/glaucia86/repo-doctor/issues) +- 💬 [Start a Discussion](https://github.com/glaucia86/repocheckai/discussions) +- 🐛 [Report an Issue](https://github.com/glaucia86/repocheckai/issues) - 📖 [Read the Full Documentation](index.md) --- @@ -328,3 +329,5 @@ AI usage is included in your GitHub Copilot subscription. There are no additiona

← Back to Documentation

+ + diff --git a/docs/getting-started.md b/docs/getting-started.md index b25e8ed..743a93d 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -1,12 +1,14 @@ # 🚀 Getting Started -This guide will help you install Repo Doctor and run your first repository health analysis. +This guide will help you install RepoCheckAI and run your first repository health analysis. + +> Transition note: use `repocheck` as the default command. Legacy `repodoctor` remains available only during the migration window. --- ## ⚡ Quick Start (5 minutes) -Want to see Repo Doctor in action? Here's how to test the GitHub issue creation feature: +Want to see RepoCheckAI in action? Here's how to test the GitHub issue creation feature: ### 1. Get a GitHub Token @@ -23,15 +25,15 @@ Want to see Repo Doctor in action? Here's how to test the GitHub issue creation export GITHUB_TOKEN=ghp_your_token_here # This may create one or multiple GitHub issues automatically, depending on findings/output format. -repo-doctor analyze your-username/your-repo --issue +repocheck analyze your-username/your-repo --issue ``` ### 3. Check the Results Visit your repository's **Issues** tab - you should see new issues like: -- 🔴 [Repo Doctor] docs: Missing README -- 🟠 [Repo Doctor] ci: No CI/CD Pipeline -- 🟡 [Repo Doctor] dx: Code Quality Issues +- 🔴 [RepoCheckAI] docs: Missing README +- 🟠 [RepoCheckAI] ci: No CI/CD Pipeline +- 🟡 [RepoCheckAI] dx: Code Quality Issues **That's it!** 🎉 Each issue contains detailed analysis, impact assessment, and fix instructions. @@ -41,7 +43,7 @@ Visit your repository's **Issues** tab - you should see new issues like: ## Prerequisites -Before installing Repo Doctor, ensure you have: +Before installing RepoCheckAI, ensure you have: ### 1. Node.js (v18+) @@ -58,7 +60,7 @@ If you need to install or update Node.js: ### 2. GitHub Copilot Subscription -Repo Doctor uses the GitHub Copilot SDK, which requires an active subscription: +RepoCheckAI uses the GitHub Copilot SDK, which requires an active subscription: - **GitHub Copilot Individual** - Works with free models (GPT-4o, GPT-4.1) - **GitHub Copilot Pro/Business/Enterprise** - Full access to premium models @@ -67,7 +69,7 @@ Repo Doctor uses the GitHub Copilot SDK, which requires an active subscription: ### 3. GitHub Copilot CLI (Required) -Repo Doctor uses the GitHub Copilot SDK, which requires the **Copilot CLI** installed: +RepoCheckAI uses the GitHub Copilot SDK, which requires the **Copilot CLI** installed: ```bash # Install Copilot CLI @@ -113,7 +115,7 @@ Then authenticate: gh auth login ``` -> **Tip:** For model access, Repo Doctor uses the GitHub CLI OAuth token. If you see `Failed to list models: 401`, follow the Copilot auth steps in [issue-publishing.md](issue-publishing.md). +> **Tip:** For model access, RepoCheckAI uses the GitHub CLI OAuth token. If you see `Failed to list models: 401`, follow the Copilot auth steps in [issue-publishing.md](issue-publishing.md). ### 5. GitHub Personal Access Token (For Publishing Features) @@ -132,7 +134,7 @@ To use advanced features like creating issues or commenting on PRs, you need a G 3. **Generate New Token** - Click **Generate new token (classic)** - - **Name**: `Repo Doctor` (or descriptive name) + - **Name**: `RepoCheckAI` (or descriptive name) - **Expiration**: Choose appropriate time (30 days recommended) - **Scopes**: Select minimal required permissions @@ -152,7 +154,7 @@ To use advanced features like creating issues or commenting on PRs, you need a G export GITHUB_TOKEN=ghp_your_token_here # Or pass it only for a single command (avoids storing it in shell history) -GITHUB_TOKEN=ghp_your_token_here repo-doctor analyze owner/repo --issue +GITHUB_TOKEN=ghp_your_token_here repocheck analyze owner/repo --issue ``` > **Full guide:** See [issue-publishing.md](issue-publishing.md) for step-by-step `--issue` setup and 401 troubleshooting. @@ -172,10 +174,10 @@ GITHUB_TOKEN=ghp_your_token_here repo-doctor analyze owner/repo --issue ```bash # 1. Clone the repository -git clone https://github.com/glaucia86/repo-doctor.git +git clone https://github.com/glaucia86/repocheckai.git # 2. Navigate to the directory -cd repo-doctor +cd repocheckai # 3. Install dependencies npm install @@ -187,7 +189,7 @@ npm run build npm link ``` -After installation, the `repo-doctor` command will be available globally. +After installation, the `repocheck` command will be available globally. ### Option 2: Development Mode @@ -195,8 +197,8 @@ If you want to contribute or modify the code: ```bash # Clone and install -git clone https://github.com/glaucia86/repo-doctor.git -cd repo-doctor +git clone https://github.com/glaucia86/repocheckai.git +cd repocheckai npm install # Run in development mode (with hot reload) @@ -206,8 +208,8 @@ npm run dev:cli ### Verify Installation ```bash -repo-doctor --version -# Should display: repo-doctor v2.x.x +repocheck --version +# Should display: repocheck v2.x.x ``` --- @@ -219,13 +221,13 @@ repo-doctor --version The easiest way to start is with interactive mode: ```bash -repo-doctor +repocheck ``` You'll see a welcome screen:

- Repo Doctor Welcome Screen + RepoCheckAI Welcome Screen

1. **Enter a repository** — Type `vercel/next.js` or any public repository @@ -239,17 +241,17 @@ You can also analyze directly from the command line: ```bash # Analyze a public repository -repo-doctor vercel/next.js +repocheck vercel/next.js # With a specific model -repo-doctor facebook/react --model gpt-4o +repocheck facebook/react --model gpt-4o # Deep analysis (comprehensive scan) -repo-doctor microsoft/typescript --deep +repocheck microsoft/typescript --deep # 🔥 NEW: Create GitHub issues automatically export GITHUB_TOKEN=ghp_your_token_here -repo-doctor analyze your-username/your-repo --issue +repocheck analyze your-username/your-repo --issue ``` ### Publishing Reports to GitHub @@ -265,122 +267,54 @@ repo-doctor analyze your-username/your-repo --issue export GITHUB_TOKEN=ghp_your_token_here # Create issues for each problem found -repo-doctor analyze your-username/your-repo --issue +repocheck analyze your-username/your-repo --issue # Result: One or multiple GitHub issues created automatically, depending on findings. ``` -#### Interactive Mode +#### Web UI (equivalent to `--issue`) ```bash -# Set token securely for the session -export GITHUB_TOKEN=ghp_your_token_here - -# Then start interactive mode -repo-doctor chat -# Then type: -/analyze facebook/react --issue -/deep microsoft/vscode +npm run dev:local-ui ``` ---- - -## 🧪 Testing Publishing Features +In the Web UI form: -Want to try the publishing features? Here's a complete step-by-step guide: +1. Enable `Publish to GitHub Issues` +2. Optional: fill `GitHub Token` +3. Run analysis -### Step 1: Get Your GitHub Token +If `GitHub Token` is empty, the backend uses `GITHUB_TOKEN` from the server environment. -1. **Go to GitHub Settings** - - Visit [github.com](https://github.com) → Your profile → **Settings** - -2. **Generate Personal Access Token** - - **Developer settings** → **Personal access tokens** → **Tokens (classic)** - - Click **"Generate new token (classic)"** - - **Name**: `Repo Doctor Test` - - **Expiration**: 7 days (for testing) - - **Scopes**: Select one of these options: - - `repo` (full control of private repositories) **OR** - - Granular permissions: - - `metadata` — Read repository metadata - - `contents` — Read repository contents - - `issues` — Create and manage issues - -3. **Copy the token** (often starts with `ghp_` or `github_pat_`) - -### Step 2: Test with Interactive Mode +#### Interactive Mode ```bash -# Set your token securely +# Set token securely for the session export GITHUB_TOKEN=ghp_your_token_here -# Start interactive mode -repo-doctor chat -``` - -### Step 3: Test Issue Creation - -```bash -# In the chat, type: +# Then start interactive mode +repocheck chat +# Then type: /analyze facebook/react --issue +/deep microsoft/vscode ``` -**What happens:** -- ✅ Analyzes the repository -- ✅ Creates a GitHub issue in `facebook/react` (if you have access) -- ✅ Or creates issues in your own repository if you don't have access to facebook/react - -### Step 4: Test with Your Own Repository - -```bash -# Use your own repository for testing -/analyze your-username/your-repo --issue -``` - -**Expected Result:** -- One or multiple issues created, depending on findings -- Each issue has detailed description, impact, and fix instructions -- Issues are labeled by category (docs, dx, ci, security, etc.) - -### Example Output - -After running `/analyze facebook/react --issue`, you should see: - -``` -✓ Analysis completed successfully! - Made 25 API calls in 45.2s - - Publishing report as GitHub issue(s)... - -✓ Report published: 3 issues created. - https://github.com/facebook/react/issues/123 - https://github.com/facebook/react/issues/124 - https://github.com/facebook/react/issues/125 -``` - -### Troubleshooting Publishing +--- -**"Repository not found"** -- Check repository name spelling -- Ensure you have access to the repository -- Try with your own repository first +## 🧪 Testing Publishing Features -**"Token permission denied"** -- Regenerate token with correct scopes -- Make sure you have `repo` scope OR the granular permissions: `metadata`, `contents`, and `issues` +Quick validation checklist: -**"No issues created"** -- The repository might be very healthy (no issues found) -- Check the analysis output for problems +1. Configure token with issue-write permission. +2. Run one CLI test (`repocheck analyze owner/repo --issue`) or one Web UI test (`npm run dev:local-ui` + enable `Publish to GitHub Issues`). +3. Confirm new issue(s) were created in the target repository. -### Security Best Practices +If publishing fails: +- `401` in model listing: Copilot auth issue (`GH_TOKEN` path). +- `401/403` in issue creation: GitHub API token scope/access issue (`GITHUB_TOKEN` path). -- **Never commit tokens** to code -- Use short-lived tokens for testing -- Revoke tokens after testing -- Consider GitHub Apps for production use - ---- +For full step-by-step setup, token scope matrix, and troubleshooting, use: +- [Issue Publishing Guide](issue-publishing.md) --- @@ -450,11 +384,11 @@ Now that you've run your first analysis: ```bash # Your organization's repos -repo-doctor your-org/your-repo +repocheck your-org/your-repo # Private repositories (requires token) export GITHUB_TOKEN=ghp_xxxxx -repo-doctor your-org/private-repo +repocheck your-org/private-repo ``` ### Publishing Features @@ -465,10 +399,10 @@ With a GitHub Personal Access Token, you can automatically publish analysis repo ```bash # Create a GitHub issue with the complete analysis -GITHUB_TOKEN=ghp_your_token repo-doctor analyze owner/repo --issue +GITHUB_TOKEN=ghp_your_token repocheck analyze owner/repo --issue # The issue includes: -# - Title: "Repo Doctor Report: owner/repo" +# - Title: "RepoCheckAI Report: owner/repo" # - Labels: Based on findings (docs, dx, ci, security, etc.) # - Body: Full analysis report in Markdown format ``` @@ -476,7 +410,7 @@ GITHUB_TOKEN=ghp_your_token repo-doctor analyze owner/repo --issue #### Interactive Mode ```bash -repo-doctor chat +repocheck chat # Then use: /analyze owner/repo --issue /deep owner/repo @@ -484,7 +418,7 @@ repo-doctor chat ### Integrate into Workflow -- Run Repo Doctor before major releases +- Run RepoCheckAI before major releases - Use it in CI/CD for automated health checks - Share reports with your team - **Auto-publish issues** for tracking repository improvements @@ -492,26 +426,26 @@ repo-doctor chat ### Join the Community -- ⭐ [Star the repository](https://github.com/glaucia86/repo-doctor) -- 🐛 [Report issues](https://github.com/glaucia86/repo-doctor/issues) -- 💡 [Suggest features](https://github.com/glaucia86/repo-doctor/discussions) +- ⭐ [Star the repository](https://github.com/glaucia86/repocheckai) +- 🐛 [Report issues](https://github.com/glaucia86/repocheckai/issues) +- 💡 [Suggest features](https://github.com/glaucia86/repocheckai/discussions) - 🤝 [Contribute](CONTRIBUTING.md) --- ## Troubleshooting Installation -### "command not found: repo-doctor" +### "command not found: repocheck" The global link wasn't created properly: ```bash # Try relinking -npm unlink repo-doctor +npm unlink repocheck npm link # Or run directly -npx repo-doctor +npx repocheck ``` ### "Cannot find module" errors @@ -544,3 +478,6 @@ See [Troubleshooting](troubleshooting.md) for more solutions. ← Back to DocumentationUser Guide →

+ + + diff --git a/docs/index.md b/docs/index.md index 2664af2..f921c0b 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,4 +1,4 @@ -# 🩺 Repo Doctor Documentation +# 🩺 RepoCheckAI Documentation

AI-powered GitHub Repository Health Analyzer @@ -6,11 +6,21 @@ --- -Welcome to the official documentation for **Repo Doctor** — an agentic CLI tool that performs comprehensive health checks on GitHub repositories using AI. +Welcome to the official documentation for **RepoCheckAI** — an agentic CLI tool that performs comprehensive health checks on GitHub repositories using AI. -## What is Repo Doctor? +## Recommended Path For Issue Publishing -Repo Doctor is your repository's AI doctor that diagnoses issues and prescribes solutions. Built with the [GitHub Copilot SDK](https://github.com/github/copilot-sdk), it analyzes repositories across **6 critical areas**: +If your goal is to publish analysis results as GitHub issues, follow this order: + +1. Read [🧭 Issue Publishing](issue-publishing.md) for token/auth setup and troubleshooting. +2. Choose your interface: + - CLI: use `--issue` + - Web UI: enable `Publish to GitHub Issues` +3. If publishing fails with `401/403`, return to the same guide and follow the diagnostics section. + +## What is RepoCheckAI? + +RepoCheckAI is your repository's AI doctor that diagnoses issues and prescribes solutions. Built with the [GitHub Copilot SDK](https://github.com/github/copilot-sdk), it analyzes repositories across **6 critical areas**: - 📚 **Documentation & Onboarding** - ⚡ **Developer Experience** @@ -93,14 +103,14 @@ Get an overall health percentage (0-100%) based on weighted category scores: ```bash # Install -git clone https://github.com/glaucia86/repo-doctor.git -cd repo-doctor && npm install && npm run build && npm link +git clone https://github.com/glaucia86/repocheckai.git +cd repocheckai && npm install && npm run build && npm link # Run interactive mode -repo-doctor +repocheck # Or analyze directly -repo-doctor vercel/next.js +repocheck vercel/next.js ``` See the [Getting Started Guide](getting-started.md) for detailed instructions. @@ -119,8 +129,8 @@ See the [Getting Started Guide](getting-started.md) for detailed instructions. ## Support -- 🐛 **Found a bug?** [Open an issue](https://github.com/glaucia86/repo-doctor/issues/new) -- 💡 **Have an idea?** [Start a discussion](https://github.com/glaucia86/repo-doctor/discussions) +- 🐛 **Found a bug?** [Open an issue](https://github.com/glaucia86/repocheckai/issues/new) +- 💡 **Have an idea?** [Start a discussion](https://github.com/glaucia86/repocheckai/discussions) - 🤝 **Want to contribute?** Read our [Contributing Guide](CONTRIBUTING.md) --- @@ -128,3 +138,5 @@ See the [Getting Started Guide](getting-started.md) for detailed instructions.

Made with 💚 by Glaucia Lemos

+ + diff --git a/docs/issue-publishing.md b/docs/issue-publishing.md index 7cfe673..8f51d9a 100644 --- a/docs/issue-publishing.md +++ b/docs/issue-publishing.md @@ -6,7 +6,7 @@ This guide explains how to use the `--issue` flag safely, how Copilot SDK auth d ## 1) Two auth paths (very important) -Repo Doctor uses two separate auth paths: +RepoCheckAI uses two separate auth paths: - **Copilot SDK auth (models and analysis)** - If this fails, you will see: `Failed to list models: 401`. @@ -37,7 +37,7 @@ gh auth login # Do NOT use GITHUB_TOKEN here gh auth status -# Export OAuth token for Repo Doctor +# Export OAuth token for RepoCheckAI $env:GH_TOKEN = (gh auth token) ``` @@ -74,7 +74,7 @@ You need a PAT that can create issues in the target repo. --- -## 4) Run Repo Doctor with `--issue` +## 4) Run RepoCheckAI with `--issue` (CLI) You can use Copilot auth (GH_TOKEN) and pass the PAT only for issue creation. @@ -95,12 +95,34 @@ In the app: Direct mode: ```powershell -repo-doctor analyze owner/repo --issue --token +repocheck analyze owner/repo --issue --token ``` --- -## 5) Quick diagnostics +## 5) Run issue publishing from Web UI + +Start both services: + +```bash +npm run dev:local-ui +``` + +In the Web UI form: + +1. Enable **Publish to GitHub Issues** +2. Optionally fill **GitHub Token** +3. Run analysis + +Token behavior in Web UI: + +- If **GitHub Token** is filled, that value is used. +- If the field is empty, the backend tries `GITHUB_TOKEN` from server environment. +- If neither is available, analysis still runs, but issue publishing is skipped. + +--- + +## 6) Quick diagnostics ### Check PAT can create an issue @@ -109,7 +131,7 @@ $env:GITHUB_TOKEN = "" Invoke-RestMethod -Method Post \ -Headers @{ Authorization = "Bearer $env:GITHUB_TOKEN" } \ -Uri https://api.github.com/repos/owner/repo/issues \ - -Body (@{ title = "Repo Doctor test"; body = "test" } | ConvertTo-Json) \ + -Body (@{ title = "RepoCheckAI test"; body = "test" } | ConvertTo-Json) \ -ContentType "application/json" ``` @@ -121,7 +143,7 @@ Invoke-RestMethod -Method Post \ --- -## 6) Security notes +## 7) Security notes - Never commit tokens or store them inside the repo - Use short expiration for PATs @@ -132,3 +154,5 @@ Invoke-RestMethod -Method Post \

← Back to Documentation

+ + diff --git a/docs/repository-layout.md b/docs/repository-layout.md index 6651324..f824b71 100644 --- a/docs/repository-layout.md +++ b/docs/repository-layout.md @@ -1,6 +1,6 @@ # 🗂️ Repository Layout -Repo Doctor currently has three application surfaces: +Repo Check AI currently has three application surfaces: - **CLI**: terminal-first workflow for repository analysis. - **Web UI**: local browser UI backed by a local API. @@ -9,7 +9,7 @@ Repo Doctor currently has three application surfaces: ## Top-Level Structure ```text -repo-doctor/ +repocheckai/ ├── site/ ├── src/ ├── tests/ @@ -54,3 +54,4 @@ Static site content deployed with GitHub Pages. - Keeps the public website isolated from runtime source code. - Separates `src/` by clean architecture layers. - Reduces accidental cross-surface edits by clarifying ownership. + diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index db48a64..14ad263 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -1,6 +1,8 @@ # 🔧 Troubleshooting -Solutions for common issues when using Repo Doctor. +Solutions for common issues when using RepoCheckAI. + +> Transition note: if old scripts still call `repodoctor`, they should keep working during migration but will emit a deprecation warning. --- @@ -18,7 +20,7 @@ Solutions for common issues when using Repo Doctor. ## Installation Issues -### "command not found: repo-doctor" +### "command not found: repocheck" The global npm link wasn't created successfully. @@ -26,11 +28,11 @@ The global npm link wasn't created successfully. ```bash # 1. Try relinking -npm unlink repo-doctor +npm unlink repocheck npm link # 2. Run directly with npx -npx repo-doctor +npx repocheck # 3. Check npm global path npm config get prefix @@ -56,7 +58,7 @@ npm run build ### "Node.js version too old" -Repo Doctor requires Node.js 18+. +RepoCheckAI requires Node.js 18+. **Solutions:** @@ -217,7 +219,7 @@ curl https://api.github.com/repos/owner/repo ```bash # 1. Increase timeout -repo-doctor owner/repo --timeout 180000 +repocheck owner/repo --timeout 180000 # 2. Use quick analysis instead of deep /analyze owner/repo # Instead of /deep @@ -226,7 +228,7 @@ repo-doctor owner/repo --timeout 180000 ping api.github.com # 4. Try a different model (some are faster) -repo-doctor owner/repo --model gpt-4o +repocheck owner/repo --model gpt-4o ``` ### "Empty repository" error @@ -264,13 +266,13 @@ The analysis took longer than the timeout limit. ```bash # Increase timeout (default: 120000ms = 2 minutes) -repo-doctor owner/repo --timeout 300000 # 5 minutes +repocheck owner/repo --timeout 300000 # 5 minutes # Use quick analysis for large repos /analyze owner/repo # Use a faster model -repo-doctor owner/repo --model gpt-4o +repocheck owner/repo --model gpt-4o ``` --- @@ -290,7 +292,7 @@ The selected model isn't available for your subscription. ```bash # Switch to a free model -repo-doctor owner/repo --model gpt-4o +repocheck owner/repo --model gpt-4o ``` ### "Copilot session error" or "SDK error" @@ -338,7 +340,7 @@ Premium models like Opus consume rate limits faster. # 2. Wait for rate limit to reset # 3. Use free models for bulk analysis -repo-doctor owner/repo --model gpt-4o +repocheck owner/repo --model gpt-4o ``` --- @@ -352,7 +354,7 @@ The file encoding might not support emojis. **Solutions:** ```bash -# Repo Doctor saves with UTF-8 BOM by default +# RepoCheckAI saves with UTF-8 BOM by default # If viewing in old editors, try: # - VS Code (recommended) # - Notepad++ with UTF-8 encoding @@ -361,11 +363,11 @@ The file encoding might not support emojis. ### Can't find exported file -**Default export location:** `~/repo-doctor/reports/` +**Default export location:** `~/repocheck/reports/` ```bash # Check default location -ls ~/repo-doctor/reports/ +ls ~/repocheck/reports/ # Export to specific location /export ~/Desktop @@ -428,7 +430,7 @@ Large repositories can use significant memory during deep analysis. /analyze owner/repo # Limit files analyzed -repo-doctor owner/repo --max-files 500 +repocheck owner/repo --max-files 500 # Close other applications during analysis ``` @@ -442,10 +444,10 @@ repo-doctor owner/repo --max-files 500 /analyze owner/repo # 2. Increase Node.js memory if needed -NODE_OPTIONS="--max-old-space-size=4096" repo-doctor owner/repo +NODE_OPTIONS="--max-old-space-size=4096" repocheck owner/repo # 3. Use faster model -repo-doctor owner/repo --model gpt-4o +repocheck owner/repo --model gpt-4o ``` ### Terminal rendering issues @@ -470,7 +472,7 @@ export LANG=en_US.UTF-8 ### Before asking for help 1. **Check this troubleshooting guide** -2. **Search existing issues:** [github.com/glaucia86/repo-doctor/issues](https://github.com/glaucia86/repo-doctor/issues) +2. **Search existing issues:** [github.com/glaucia86/repocheckai/issues](https://github.com/glaucia86/repocheckai/issues) 3. **Read the FAQ:** [faq.md](faq.md) ### Reporting a bug @@ -486,7 +488,7 @@ Create an issue with: # Include this info node --version npm --version -repo-doctor --version # If available +repocheck --version # If available ``` 5. **Error messages** — Full error output @@ -496,8 +498,8 @@ repo-doctor --version # If available | Channel | Best For | |---------|----------| -| [GitHub Issues](https://github.com/glaucia86/repo-doctor/issues) | Bug reports | -| [GitHub Discussions](https://github.com/glaucia86/repo-doctor/discussions) | Questions, ideas | +| [GitHub Issues](https://github.com/glaucia86/repocheckai/issues) | Bug reports | +| [GitHub Discussions](https://github.com/glaucia86/repocheckai/discussions) | Questions, ideas | | [Twitter @glaucia_lemos86](https://twitter.com/glaucia_lemos86) | Quick questions | --- @@ -506,7 +508,7 @@ repo-doctor --version # If available | Problem | Quick Fix | |---------|-----------| -| Command not found | `npm link` or use `npx repo-doctor` | +| Command not found | `npm link` or use `npx repocheck` | | Module errors | `rm -rf node_modules && npm install` | | Auth failure | `export GITHUB_TOKEN=ghp_xxx` | | Rate limited | Wait 1 hour or use token | @@ -520,3 +522,6 @@ repo-doctor --version # If available

← Back to Documentation

+ + + diff --git a/package-lock.json b/package-lock.json index 3e0be03..b1106c6 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,15 +1,15 @@ { - "name": "repo-doctor", + "name": "repocheckai", "version": "2.4.0", "lockfileVersion": 3, "requires": true, "packages": { "": { - "name": "repo-doctor", + "name": "repocheckai", "version": "2.4.0", "license": "MIT", "dependencies": { - "@github/copilot-sdk": "~0.1.23", + "@github/copilot-sdk": "~0.1.24", "@inquirer/prompts": "~8.2.0", "@octokit/rest": "~22.0.1", "chalk": "~5.3.0", @@ -24,7 +24,8 @@ "zod": "~3.22.0" }, "bin": { - "repo-doctor": "dist/index.js" + "repocheck": "dist/index.js", + "repodoctor": "dist/index.js" }, "devDependencies": { "@types/commander": "^2.12.0", @@ -1223,26 +1224,26 @@ } }, "node_modules/@github/copilot": { - "version": "0.0.403", - "resolved": "https://registry.npmjs.org/@github/copilot/-/copilot-0.0.403.tgz", - "integrity": "sha512-v5jUdtGJReLmE1rmff/LZf+50nzmYQYAaSRNtVNr9g0j0GkCd/noQExe31i1+PudvWU0ZJjltR0B8pUfDRdA9Q==", + "version": "0.0.409", + "resolved": "https://registry.npmjs.org/@github/copilot/-/copilot-0.0.409.tgz", + "integrity": "sha512-rkYWOKjTSuGg99KsgmA0QAP4X2cpJzAYk6lZDlVxKPhuLP03wC5E+jLctrSLjpxhX32p9n13rm1+7Jun80a1hw==", "license": "SEE LICENSE IN LICENSE.md", "bin": { "copilot": "npm-loader.js" }, "optionalDependencies": { - "@github/copilot-darwin-arm64": "0.0.403", - "@github/copilot-darwin-x64": "0.0.403", - "@github/copilot-linux-arm64": "0.0.403", - "@github/copilot-linux-x64": "0.0.403", - "@github/copilot-win32-arm64": "0.0.403", - "@github/copilot-win32-x64": "0.0.403" + "@github/copilot-darwin-arm64": "0.0.409", + "@github/copilot-darwin-x64": "0.0.409", + "@github/copilot-linux-arm64": "0.0.409", + "@github/copilot-linux-x64": "0.0.409", + "@github/copilot-win32-arm64": "0.0.409", + "@github/copilot-win32-x64": "0.0.409" } }, "node_modules/@github/copilot-darwin-arm64": { - "version": "0.0.403", - "resolved": "https://registry.npmjs.org/@github/copilot-darwin-arm64/-/copilot-darwin-arm64-0.0.403.tgz", - "integrity": "sha512-dOw8IleA0d1soHnbr/6wc6vZiYWNTKMgfTe/NET1nCfMzyKDt/0F0I7PT5y+DLujJknTla/ZeEmmBUmliTW4Cg==", + "version": "0.0.409", + "resolved": "https://registry.npmjs.org/@github/copilot-darwin-arm64/-/copilot-darwin-arm64-0.0.409.tgz", + "integrity": "sha512-yjrrp++UNNvRoWsZ1+UioBqb3DEVxL5M5ePnMO5/Sf1sngxh0y5P9P6ePFZU4PVlM5BgC38DtrcauZaKf/oArQ==", "cpu": [ "arm64" ], @@ -1256,9 +1257,9 @@ } }, "node_modules/@github/copilot-darwin-x64": { - "version": "0.0.403", - "resolved": "https://registry.npmjs.org/@github/copilot-darwin-x64/-/copilot-darwin-x64-0.0.403.tgz", - "integrity": "sha512-aK2jSNWgY8eiZ+TmrvGhssMCPDTKArc0ip6Ul5OaslpytKks8hyXoRbxGD0N9sKioSUSbvKUf+1AqavbDpJO+w==", + "version": "0.0.409", + "resolved": "https://registry.npmjs.org/@github/copilot-darwin-x64/-/copilot-darwin-x64-0.0.409.tgz", + "integrity": "sha512-EhLfY5DGU/BZmwjVcfnwKuJA7BxS9zdNCGeynUq7z/SI93ziastFqOddUX4D+ySz6yMrrXieN8cUKgzAlRCOJg==", "cpu": [ "x64" ], @@ -1272,9 +1273,9 @@ } }, "node_modules/@github/copilot-linux-arm64": { - "version": "0.0.403", - "resolved": "https://registry.npmjs.org/@github/copilot-linux-arm64/-/copilot-linux-arm64-0.0.403.tgz", - "integrity": "sha512-KhoR2iR70O6vCkzf0h8/K+p82qAgOvMTgAPm9bVEHvbdGFR7Py9qL5v03bMbPxsA45oNaZAkzDhfTAqWhIAZsQ==", + "version": "0.0.409", + "resolved": "https://registry.npmjs.org/@github/copilot-linux-arm64/-/copilot-linux-arm64-0.0.409.tgz", + "integrity": "sha512-O7b/9LmBO8ljPqNngonx+v5d3cOs6HKvj2E9f5/Flb9Uw2lut7g6KGerfDYCMZUpvFCMDfbZSBJD3SDuJj1uPg==", "cpu": [ "arm64" ], @@ -1288,9 +1289,9 @@ } }, "node_modules/@github/copilot-linux-x64": { - "version": "0.0.403", - "resolved": "https://registry.npmjs.org/@github/copilot-linux-x64/-/copilot-linux-x64-0.0.403.tgz", - "integrity": "sha512-eoswUc9vo4TB+/9PgFJLVtzI4dPjkpJXdCsAioVuoqPdNxHxlIHFe9HaVcqMRZxUNY1YHEBZozy+IpUEGjgdfQ==", + "version": "0.0.409", + "resolved": "https://registry.npmjs.org/@github/copilot-linux-x64/-/copilot-linux-x64-0.0.409.tgz", + "integrity": "sha512-zSfFqyPxNaBE5/ClrSjsKxhhTpJaVOqSJY0q87iV9fw6xwdzcJ1/FlZGKjE7W8YVb4tdJx+OBMjQCU8WYewF1A==", "cpu": [ "x64" ], @@ -1304,17 +1305,17 @@ } }, "node_modules/@github/copilot-sdk": { - "version": "0.1.23", - "resolved": "https://registry.npmjs.org/@github/copilot-sdk/-/copilot-sdk-0.1.23.tgz", - "integrity": "sha512-0by81bsBQlDKE5VbcegZfUMvPyPm1aXwSGS2rGaMAFxv3ps+dACf1Voruxik7hQTae0ziVFJjuVrlxZoRaXBLw==", + "version": "0.1.24", + "resolved": "https://registry.npmjs.org/@github/copilot-sdk/-/copilot-sdk-0.1.24.tgz", + "integrity": "sha512-BkP4OCrB8zFYS77JhzbAfB9xCzpUN6h2XTUsWQJaTR2xSvyBdXulrpXaeF2P2tOE5R4/sozDpjRtPgwz0v8V5Q==", "license": "MIT", "dependencies": { - "@github/copilot": "^0.0.403", + "@github/copilot": "^0.0.409", "vscode-jsonrpc": "^8.2.1", "zod": "^4.3.6" }, "engines": { - "node": ">=24.0.0" + "node": ">=20.0.0" } }, "node_modules/@github/copilot-sdk/node_modules/zod": { @@ -1327,9 +1328,9 @@ } }, "node_modules/@github/copilot-win32-arm64": { - "version": "0.0.403", - "resolved": "https://registry.npmjs.org/@github/copilot-win32-arm64/-/copilot-win32-arm64-0.0.403.tgz", - "integrity": "sha512-djWjzCsp2xPNafMyOZ/ivU328/WvWhdroGie/DugiJBTgQL2SP0quWW1fhTlDwE81a3g9CxfJonaRgOpFTJTcg==", + "version": "0.0.409", + "resolved": "https://registry.npmjs.org/@github/copilot-win32-arm64/-/copilot-win32-arm64-0.0.409.tgz", + "integrity": "sha512-VizZsdK7L3ym/OR4wahiFx+6hFtaOYN9qvsHmNSo8pb65AZ6ORdRnCPE7w9ZejMpdNEa6x6WqHfxDKJlF85zyA==", "cpu": [ "arm64" ], @@ -1343,9 +1344,9 @@ } }, "node_modules/@github/copilot-win32-x64": { - "version": "0.0.403", - "resolved": "https://registry.npmjs.org/@github/copilot-win32-x64/-/copilot-win32-x64-0.0.403.tgz", - "integrity": "sha512-lju8cHy2E6Ux7R7tWyLZeksYC2MVZu9i9ocjiBX/qfG2/pNJs7S5OlkwKJ0BSXSbZEHQYq7iHfEWp201bVfk9A==", + "version": "0.0.409", + "resolved": "https://registry.npmjs.org/@github/copilot-win32-x64/-/copilot-win32-x64-0.0.409.tgz", + "integrity": "sha512-c6dP3XRFk550PmH1Vxe7n/bStNSLnVGH5B+ErUKXk/SPqmZ59pyoa7H2USNdoC6Nav5tkwYYR1vwNZRy+iKvrA==", "cpu": [ "x64" ], diff --git a/package.json b/package.json index 22ce70a..85b9c0d 100644 --- a/package.json +++ b/package.json @@ -1,11 +1,13 @@ { - "name": "repo-doctor", + "name": "repocheckai", "version": "2.4.0", "description": "AI-powered GitHub repository health analyzer using GitHub Copilot SDK", "main": "dist/index.js", "type": "module", "bin": { - "repo-doctor": "./dist/index.js" + "repocheck": "./dist/index.js", + "repo-doctor": "./dist/index.js", + "repodoctor": "./dist/index.js" }, "files": [ "dist", @@ -46,7 +48,7 @@ }, "repository": { "type": "git", - "url": "https://github.com/glaucia86/repo-doctor.git" + "url": "https://github.com/glaucia86/repocheckai.git" }, "keywords": [ "github", @@ -65,11 +67,11 @@ "author": "Glaucia Lemos", "license": "MIT", "bugs": { - "url": "https://github.com/glaucia86/repo-doctor/issues" + "url": "https://github.com/glaucia86/repocheckai/issues" }, - "homepage": "https://github.com/glaucia86/repo-doctor#readme", + "homepage": "https://github.com/glaucia86/repocheckai#readme", "dependencies": { - "@github/copilot-sdk": "~0.1.23", + "@github/copilot-sdk": "~0.1.24", "@inquirer/prompts": "~8.2.0", "@octokit/rest": "~22.0.1", "chalk": "~5.3.0", @@ -89,18 +91,18 @@ "@types/node": "^25.2.3", "@types/react": "^18.3.12", "@types/react-dom": "^18.3.1", - "@vitejs/plugin-react": "^4.4.1", "@typescript-eslint/eslint-plugin": "^8.55.0", "@typescript-eslint/parser": "^8.55.0", + "@vitejs/plugin-react": "^4.4.1", "@vitest/coverage-v8": "^4.0.18", - "axe-core": "^4.11.1", "autoprefixer": "^10.4.21", + "axe-core": "^4.11.1", "eslint": "^9.0.0", "eslint-config-prettier": "^9.1.0", "husky": "^9.1.6", "jsdom": "^28.0.0", - "postcss": "^8.5.6", "png-to-ico": "^3.0.1", + "postcss": "^8.5.6", "prettier": "^3.3.3", "sharp": "^0.34.5", "tailwindcss": "^3.4.17", diff --git a/resources/banner.svg b/resources/banner.svg index 363f67d..7348a2a 100644 --- a/resources/banner.svg +++ b/resources/banner.svg @@ -1,60 +1,88 @@ - + + RepoCheckAI Banner + Technology banner with repository graph mark and RepoCheckAI wordmark. + - - - + + + + - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + - - - - Repo Doctor - - - - - AI-powered GitHub Repository Health Analyzer - - - - - - Copilot SDK - - - TypeScript - - - CLI + + + + RepoCheckAI + + + AI-powered GitHub Repository Health Analyzer + - - - - - + + + + GITHUB COPILOT SDK + + + TYPESCRIPT + + + CLI diff --git a/resources/how-it-works.excalidraw b/resources/how-it-works.excalidraw index e5eca79..211ec19 100644 --- a/resources/how-it-works.excalidraw +++ b/resources/how-it-works.excalidraw @@ -1079,13 +1079,13 @@ "strokeStyle": "solid", "roughness": 1, "opacity": 100, - "text": "🩺 How Repo Doctor Works", + "text": "🩺 How Repo Check AI Works", "fontSize": 36, "fontFamily": 5, "textAlign": "center", "verticalAlign": "middle", - "version": 388, - "versionNonce": 1521777022, + "version": 413, + "versionNonce": 1507786882, "index": "aT", "isDeleted": false, "seed": 1, @@ -1093,11 +1093,11 @@ "frameId": null, "roundness": null, "boundElements": [], - "updated": 1769210783886, + "updated": 1771296156698, "link": null, "locked": false, "containerId": null, - "originalText": "🩺 How Repo Doctor Works", + "originalText": "🩺 How Repo Check AI Works", "autoResize": false, "lineHeight": 1.25 } diff --git a/resources/how-it-works.png b/resources/how-it-works.png index 71ea22b..1055fff 100644 Binary files a/resources/how-it-works.png and b/resources/how-it-works.png differ diff --git a/resources/image.png b/resources/image.png index ca6f36c..4c49b82 100644 Binary files a/resources/image.png and b/resources/image.png differ diff --git a/resources/repo-check-ai-web.png b/resources/repo-check-ai-web.png new file mode 100644 index 0000000..29212b9 Binary files /dev/null and b/resources/repo-check-ai-web.png differ diff --git a/resources/repo-doctor-ui.png b/resources/repo-doctor-ui.png deleted file mode 100644 index 8a1f856..0000000 Binary files a/resources/repo-doctor-ui.png and /dev/null differ diff --git a/site/404.html b/site/404.html index c5abe8b..333da53 100644 --- a/site/404.html +++ b/site/404.html @@ -5,9 +5,10 @@ - Repo Doctor + Repo Check AI

Redirecting to home page...

+ diff --git a/site/README.md b/site/README.md index 6423352..24cbe69 100644 --- a/site/README.md +++ b/site/README.md @@ -1,7 +1,8 @@ # Site App -Static website for Repo Doctor. +Static website for Repo Check AI. - Location: `site/**` - Deployment workflow: `.github/workflows/pages.yml` - GitHub Pages artifact path: `site` + diff --git a/site/about.html b/site/about.html index 504e7c8..4af5eb9 100644 --- a/site/about.html +++ b/site/about.html @@ -3,30 +3,30 @@ - About | Repo Doctor + About | RepoCheckAI - + - + - + - - + + @@ -40,7 +40,7 @@
- Repo Doctor + RepoCheckAI
- + Star on GitHub Try Web UI @@ -62,20 +62,20 @@
About the Creator

- I am Glaucia Lemos, AI Software Engineer and creator of Repo Doctor for teams + I am Glaucia Lemos, AI Software Engineer and creator of RepoCheckAI for teams that want to ship with clarity.

I build AI applications with JavaScript/TypeScript, backed by deep experience in backend and cloud - engineering. Repo Doctor was built to help teams replace guesswork with evidence-based technical decisions. + engineering. RepoCheckAI was built to help teams replace guesswork with evidence-based technical decisions.

- Repo Doctor is completely open source, from core logic to community contributions. The goal is simple: + RepoCheckAI is completely open source, from core logic to community contributions. The goal is simple: build in public, improve in public, and keep repository health accessible to every engineering team.

@@ -109,7 +109,7 @@

The story behind the project

My career has always been connected to software quality, technical clarity, and developer education.

- Repo Doctor came from a recurring pattern: many repositories do not fail because of bad code, but because + RepoCheckAI came from a recurring pattern: many repositories do not fail because of bad code, but because quality signals are disconnected. Documentation, CI/CD, governance, and security often evolve at different speeds.

@@ -173,7 +173,7 @@

Problem identified

2025

First prototype

-

The first Repo Doctor version shipped with evidence-first analysis and a P0/P1/P2 prioritization model.

+

The first RepoCheckAI version shipped with evidence-first analysis and a P0/P1/P2 prioritization model.

@@ -242,7 +242,7 @@

Let's build the future of repo health together.