Build a Repository Bug-Fixing Agent
Build an agent that turns a bug report into a reproducible failure, a code patch, and a reviewable change package. Let maintainers inspect the evidence before accepting the fix.
What you are building
The core problem, expected build, and operating context for this challenge.
A software maintainer handling incoming bug reports.
Build an agent that turns a bug report into a reproducible failure, a code patch, and a reviewable change package. Let maintainers inspect the evidence before accepting the fix.
Issue description
Local repository files
Allowed test commands
Read the issue and inspect relevant files.
Create a failing reproduction test.
Implement the smallest supported fix.
Run the allowed checks and assemble a local change package.
An issue workspace with reproduction logs, a code diff, test results, and an accept-or-reject review panel.
Import the repository, reproduce total(100, 10) returning 110, fix it to return 90, and display passing tests with the diff.
A working local application with the specified review interface.
Source code, dependency lockfile, and setup commands.
A recorded end-to-end demo using the supplied starter data.
Example outputs, action logs, and automated tests.
These fictional records are a small development fixture, not a production dataset. Implement the mock services described in the brief.
```json { "request": "Fix discounts being charged as an addition.", "files": { "pricing.py": "def total(price, discount):\n return price + discount\n", "test_pricing.py": "from pricing import total\ndef test_no_discount():\n assert total(100, 0) == 100\n" }, "issue": { "price": 100, "discount": 10, "expected_total": 90 }, "allowed_commands": [ "pytest" ] } ```
Run code only in an isolated local workspace. Do not push commits or open remote pull requests. Choose an available model that supports your implementation. Record its identifier and version.
Review the complete application, not only the starter-case answers.
The new regression test fails on the original code.
The existing test and regression test pass after the change.
The review package contains a diff and actual test logs. Add one normal case, one incomplete-input case, and one failure-recovery case.
Participation guide
Run code only in an isolated local workspace. Do not push commits or open remote pull requests.
How work is evaluated
Review workflow completion, interface usability, evidence quality, and safe failure handling. No agent execution has been verified.
A working local application with the specified review interface. Source code, dependency lockfile, and setup commands. A recorded end-to-end demo using the supplied starter data. Example outputs, action logs, and automated tests.
Challenge datasets
Public datasets, plus the private datasets you have access to.
What you should walk away with
Read the issue and inspect relevant files.
Create a failing reproduction test.
Implement the smallest supported fix.
Run the allowed checks and assemble a local change package.
Reference links and supporting material
Supplied fictional starter records: Issue description, Local repository files, Allowed test commands. The overview includes the complete JSON bundle. Implement local mock services and extend the sample coverage.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
LangGraph
Runtime for stateful agent workflows.
Evaluated output
No output checks are configured.
- No evaluation checks are configured.
- 1 public reference case
- 1 configured tool
Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.
View technical recipe
Configured tools
- LangGraph ยท Optional
Evaluation contract
- No evaluation checks are configured.
Reference cases
- 1 public reference case
Workflow tasks
No workflow tasks are configured.
Recipe freeze marker
No recipe freeze time is recorded.