22 lines
946 B
Markdown
22 lines
946 B
Markdown
# SWE-bench Task: Fix the Issue
|
|
|
|
You are solving a software engineering task from the SWE-bench benchmark.
|
|
|
|
## Problem Statement
|
|
|
|
{{ input }}
|
|
|
|
## Instructions
|
|
|
|
1. **Understand the problem**: Read the problem statement carefully. Identify which files and functions are involved.
|
|
2. **Explore the codebase**: Use Read, Glob, and Grep to find the relevant source files. Understand the existing code before making changes.
|
|
3. **Implement a minimal fix**: Make the smallest change that correctly solves the problem. Do not refactor unrelated code.
|
|
4. **Verify your fix**: Run the project's test suite to confirm your changes work and do not break existing tests.
|
|
|
|
## Constraints
|
|
|
|
- Make minimal, focused changes — only modify what is necessary to fix the issue.
|
|
- Do not add unrelated improvements, documentation, or refactoring.
|
|
- Do not create new files unless the fix requires it.
|
|
- Ensure all existing tests continue to pass after your changes.
|