This is a submission for the GitHub Copilot CLI Challenge
What I Built
I built Repo-Pulse, a high-speed repository health diagnostic tool that calculates an "Overall Health Score" based on documentation, git history, and project hygiene.
The goal of this project was to solve "Project Debt"—that common situation where a repository is functional but lacks the professional "finishing touches" (like a proper license, a clean .gitignore, or a readable README) that make it open-source ready. Repo-Pulse provides a 30-second "vibe check," generating a weighted health score and offering an automated --fix engine to generate missing boilerplate files instantly.
Demo
The tool is designed for easy testing. No credentials required.
GitHub Repository: https://github.com/mobrahi/repo-pulse
How to test it:
pip install -e .
Run repo-pulse to see your current score.
Delete your LICENSE and run repo-pulse --fix to see the auto-remediation engine in action!
My Experience with GitHub Copilot CLI
I treated GitHub Copilot (leveraging the Claude 4.5 Haiku model) as my Lead Architect rather than just a code generator.
How it impacted my development:
Enforcing Quality Gates: Right from the start, I prompted the CLI to maintain strict type-hinting and PEP 8 standards. This turned a "quick hack" into a professional-grade package.
Intelligent Filtering: When building the file-counting logic, Copilot correctly identified that we needed to exclude "noise" directories (like .venv, pycache, and node_modules) to give an accurate project size reading.
Zero-Friction Pivoting: When I decided to add the --fix feature mid-build, the AI seamlessly adapted the existing argparse structure to include the new logic, demonstrating the agility of AI-pair programming.
Error Resilience: Copilot proactively suggested try/except blocks for the Git subprocess calls, ensuring the tool doesn't crash if run in a directory without a Git history.
Using the Copilot CLI allowed me to focus 100% on the intent and ux of the tool, while the AI handled the boilerplate and technical edge cases. It turned what would have been a few hours of documentation-diving into a 30-minute creative sprint.
Top comments (0)