When builds or tests fail, most devs lose time figuring out root cause and writing the fix. FixForward turns one command into a full recovery workflow:
fixforward run
It detects failures, classifies the issue, asks GitHub Copilot CLI to generate a minimal patch, applies it on a safe branch, re-runs tests to verify, and generates a PR description — all in your terminal.
tests fail → parse output → classify failure → Copilot generates fix → apply on branch → verify → PR report
│ │ │ │ │ │ │
pytest extract regex gh copilot -p git branch re-run markdown
npm test failures heuristics "fix this bug..." safe commit tests PR body
cargo test diff
- Detect — finds
pytest.ini,package.json, orCargo.tomlto identify your ecosystem - Run tests — executes the test suite and captures the raw output
- Parse — extracts individual test failures with file paths, line numbers, and error messages
- Classify — categorizes failures (dependency, syntax, assertion, API change, env mismatch, lint, flaky)
- Generate patch — sends failure context to GitHub Copilot CLI (
gh copilot -p) for a minimal fix - Apply — creates a
fixforward/auto-*branch, writes the fix, commits - Verify — re-runs the test suite, shows before/after comparison with confidence score
- Report — generates PR title and body with what changed and why
Full autopilot run![]() |
Diagnose mode![]() |
Dependency detection![]() |
Node.js / Jest support![]() |
| Ecosystem | Test Command | Parser |
|---|---|---|
| Python | pytest --tb=long -v |
Extracts failures, tracebacks, assertion details |
| Node.js | npm test |
Supports Jest and Mocha output formats |
| Rust | cargo test |
Parses panics, assert_eq! failures, test summaries |
| Feature | Description |
|---|---|
| Auto-detect | Identifies Python, Node, or Rust projects automatically |
| Smart classification | Categorizes failures: dependency, syntax, assertion, API change, env, lint, flaky |
| Copilot-powered fixes | Uses gh copilot -p to generate minimal patches |
| Safe branches | Always applies fixes on a fixforward/auto-* branch, never touches your working branch |
| Before/after verification | Re-runs tests and shows what changed |
| Confidence scoring | 0-100% score based on how many failures were fixed |
| PR report generation | Ready-to-use PR title and body in Markdown |
| Dry-run mode | Preview the diagnosis without applying any changes |
| Rollback | One command to undo everything: fixforward rollback |
| Patch preview | See the exact diff before confirming |
pip install fixforwardOr install from source:
git clone https://github.com/stackmasteraliza/fixforward.git
cd fixforward
pip install -e .- Python 3.9+
- GitHub CLI (
gh) installed and authenticated - GitHub Copilot CLI —
gh copilotmust be available - Git installed and in PATH
# Full autopilot: detect, fix, verify, report
fixforward run
# Specify a project path
fixforward run --path ~/projects/my-broken-app
# Dry run: see diagnosis without applying fixes
fixforward run --dry-run
# Skip confirmation prompt
fixforward run --no-confirm
# Diagnose only: detect and classify failures
fixforward diagnose
# Diagnose with JSON output
fixforward diagnose --json
# Undo the last fix
fixforward rollbackYou can also run it as a Python module:
python -m fixforward run --path ./my-project| Flag | Description |
|---|---|
--path, -p |
Path to the project (default: .) |
--dry-run, -n |
Show diagnosis without applying fixes |
--no-confirm |
Skip the patch confirmation prompt |
--no-animate |
Disable loading animations |
--verbose |
Show raw Copilot CLI output |
| Flag | Description |
|---|---|
--path, -p |
Path to the project (default: .) |
--json |
Output classification as JSON |
--no-animate |
Disable loading animations |
| Flag | Description |
|---|---|
--path, -p |
Path to the project (default: .) |
The repo includes ready-made broken demo projects you can test with:
# Clone the repo
git clone https://github.com/stackmasteraliza/fixforward.git
cd fixforward
# 1. See the bug — test_divide expects integer division but gets float
cat demo/broken_python/app.py
# 2. Diagnose the failure
fixforward diagnose --path demo/broken_python
# 3. Full autopilot — Copilot fixes a / b → a // b
fixforward run --path demo/broken_python
# 4. Undo and restore the broken state
fixforward rollback --path demo/broken_python# truncate() produces ".." instead of "..."
fixforward diagnose --path demo/broken_node# clamp() uses >= instead of > for the max boundary
fixforward diagnose --path demo/broken_rustfixforward run --path demo/broken_python --dry-runThis runs detection, test execution, and classification but stops before calling Copilot or modifying any files.
fixforward diagnose --path demo/broken_python --jsonReturns structured JSON with test name, file, line, category, confidence, and error message for each failure.
FixForward classifies failures using regex heuristics for instant, deterministic results:
| Category | Examples | Confidence |
|---|---|---|
| syntax_error | SyntaxError, IndentationError, Unexpected token |
95% |
| dependency | ModuleNotFoundError, Cannot find module, ImportError |
90% |
| api_change | AttributeError, TypeError (wrong args), has no member |
85% |
| assertion | AssertionError, assert_eq!, expect().toEqual() |
85% |
| env_mismatch | Version conflicts, missing commands, engine incompatible | 80% |
| lint | Flake8, ESLint, Clippy warnings | 75% |
| flaky_test | Timeouts, connection refused, intermittent | 60% |
FixForward is designed to be safe by default:
- Never modifies your working branch — all fixes go on
fixforward/auto-*branches - Stashes dirty state — if you have uncommitted changes, they're stashed and restored on rollback
- Patch preview — see the exact diff before confirming
- Dry-run mode — diagnose without touching anything
- One-command rollback —
fixforward rollbackrestores everything - State persistence — rollback info stored at
~/.fixforward/state.json
This project was built using GitHub Copilot CLI as part of the GitHub Copilot CLI Challenge on DEV. Copilot CLI is central to the tool — it powers the actual fix generation via gh copilot -p:
# How FixForward uses Copilot CLI internally:
gh copilot -- -p "I have a python project with failing tests.
The test test_divide in test_app.py fails with AssertionError:
assert 3.333 == 3. Generate a minimal fix..." \
--allow-all-tools --add-dir ./project --silentCopilot CLI reads the source files, understands the context, and generates the smallest possible code change. FixForward then applies it, verifies it, and reports the result.
Copilot CLI prompts used
Fix generation prompt (sent via gh copilot -- -p):
I have a {ecosystem} project with failing tests. Generate a minimal fix.
FAILURES:
- [assertion] test_divide
File: test_app.py
Error: assert 3.3333333333333335 == 3
SOURCE FILES:
--- app.py ---
{file contents}
Generate the smallest possible code change to fix these failures.
Show the complete corrected file content for each file that needs changes.
Format each fix as:
FILE: <filepath>
```<complete corrected file content>```
Then explain what you changed and why.
Failure explanation prompt (used by fixforward diagnose):
Explain this test failure concisely:
Test: test_divide
File: test_app.py
Error: assert 3.3333333333333335 == 3
Category: assertion
What is the likely root cause and how should it be fixed?
fixforward/
├── cli.py # argparse CLI with run/diagnose/rollback commands
├── detector.py # Ecosystem detection + test runner (subprocess)
├── classifier.py # Regex heuristic failure classification
├── copilot.py # GitHub Copilot CLI integration (gh copilot -p)
├── patcher.py # Safe branch creation + file patching
├── verifier.py # Test re-run + confidence scoring
├── reporter.py # PR title/body generation
├── display.py # Rich-based terminal UI
├── state.py # Rollback state persistence
└── parsers/
├── pytest_parser.py # pytest output parser
├── npm_parser.py # Jest/Mocha output parser
└── cargo_parser.py # cargo test output parser
Only dependency: rich — everything else is Python stdlib.
- Python 3.9+
- Git installed and in PATH
- GitHub CLI (
gh) with Copilot access - Terminal with color support
MIT License — see LICENSE for details.
If you like this project, give it a star!





