The latest articles on Forem by ejfx (@ejfxgit2025). https://forem.com/ejfxgit2025 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3750944%2Fea179611-df4c-4f95-812b-84146eb9fd8e.jpeg https://forem.com/ejfxgit2025 en ejfx Wed, 04 Feb 2026 17:02:53 +0000 https://forem.com/ejfxgit2025/copilot-commit-crystalball-catch-risky-commits-before-they-break-your-code-4in6 https://forem.com/ejfxgit2025/copilot-commit-crystalball-catch-risky-commits-before-they-break-your-code-4in6 <p>Git commits are easy.<br><br> Good commits are not.</p> <p>Most of us have pushed code that worked locally but later caused bugs, confusion, or regret. Sometimes the change was risky. Sometimes the commit message was unclear. Sometimes we just moved too fast.</p> <p>That’s why I built Copilot Commit Crystalball 🔮.</p> <h2> What is Copilot Commit Crystalball? </h2> <p>Copilot Commit Crystalball is a CLI tool that reviews your staged Git changes and predicts what might go wrong before you commit.</p> <p>It acts like a pause button for your Git workflow.</p> <p>Before you run <code>git commit</code>, Crystalball:</p> <ul> <li>Reviews the files you staged</li> <li>Uses GitHub Copilot CLI for analysis</li> <li>Warns you about risks, bugs, and unclear code</li> </ul> <h2> Why this exists </h2> <p>Many developers commit without fully understanding:</p> <ul> <li>What exactly changed</li> <li>Whether the change is risky</li> <li>If the code is incomplete or broken</li> <li>If documentation or context is missing</li> </ul> <p>Crystalball helps you reflect before committing, not after something breaks.</p> <h2> What it checks </h2> <p>Crystalball analyzes only staged files and can detect:</p> <ul> <li>Broken or incomplete code</li> <li>Risky or unclear changes</li> <li>Poor commit practices</li> <li>Missing structure or documentation</li> <li>Debug or test code committed by mistake</li> </ul> <p>If Copilot is unavailable, it safely falls back to local analysis.</p> <h2> Example test </h2> <p>I tested Crystalball with a deliberately broken HTML file containing:</p> <ul> <li>Missing closing tags</li> <li>Broken JavaScript</li> <li>Invalid structure</li> </ul> <p>After staging the file and running Crystalball, it correctly reported:</p> <ul> <li>Missing closing tags</li> <li>Broken JavaScript logic</li> <li>Invalid HTML structure</li> <li>High overall risk level</li> </ul> <h2> Why this workflow works </h2> <ul> <li>No GitHub Actions required</li> <li>No online demo needed</li> <li>Runs locally in the terminal</li> <li>Fits real developer workflows</li> <li>Works on Windows CMD</li> </ul> <p>Crystalball doesn’t block commits — it helps you think before making them.</p> <h2> Built for the GitHub Copilot CLI Challenge </h2> <p>This project explores how GitHub Copilot CLI can improve real-world developer workflows directly from the terminal.</p> <p>Source code:<br><br> <a href="https://github.com/ejfxgit2025/copilot-commit-crystalball" rel="noopener noreferrer">https://github.com/ejfxgit2025/copilot-commit-crystalball</a></p> githubchallenge githubcopilot cli git