A Bug Finder CLI to explore your application bugs

Bipin Maharjan — Sun, 15 Feb 2026 07:24:34 +0000

This is a submission for the GitHub Copilot CLI Challenge

What I Built

I built a Bug Finder CLI tool powered by the GitHub Copilot SDK. The tool analyzes a bug ticket, reasons about it, and scans the codebase to identify likely root causes and relevant files.

This project was inspired by a real problem at work: tracking a reported bug across a large codebase often takes hours. Understanding the context, tracing dependencies, and identifying potential breakpoints is time-consuming and mentally expensive.

This tool performs the preliminary investigation automatically. It:

Interprets the bug ticket
Searches the repository for related code paths
Highlights potential problem areas
Suggests next debugging steps

Instead of starting from scratch, I begin with structured insights. It reduces investigation time and lets me focus on solving the problem rather than locating it.

Demo

Link to the demo vide:

My Experience with GitHub Copilot CLI

As a full-time software engineer, I have limited time for side projects. To make this feasible, I set up GitHub Copilot CLI on my home Raspberry Pi and built the entire application using it.

The CLI-based workflow fit perfectly with how I work. I would:

Prompt Copilot to implement or refactor features
Let it generate code
Review, test, and iterate

Features like plan mode, diff view, code review, and model reasoning control significantly improved productivity.

The experience was strong overall, but a few improvements would make it even better:

An “undo last prompt” feature
Faster navigation between previous prompts

Despite that, Copilot CLI dramatically reduced the friction of building and experimenting.

For getting started follow these:

Usage
Readme

Forem: Bipin Maharjan

A Bug Finder CLI to explore your application bugs

What I Built

Demo

My Experience with GitHub Copilot CLI

For getting started follow these:

Links