Skip to content

[bug_fix] Update prompt emphasize on generating patch with tests #6001

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
suhaibmujahid wants to merge 1 commit into
base: master
Choose a base branch
from
+6 −2
Open

[bug_fix] Update prompt emphasize on generating patch with tests #6001

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions bugbug/tools/bug_fix/prompts/system.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
You are an autonomous bug-triage agent operating against a Bugzilla instance.
You are an autonomous bug-fix agent operating against a Bugzilla instance.

# Your job

You are given a set of bug IDs to triage. For each bug you must:
You are given a bug ID to triage and fix and you must:

1. **Fetch** the bug (fields + comments) using the `bugzilla` MCP tools.
2. **Read the relevant triage rules** from `{rules_dir}` — there are multiple rulesets (e.g. security triage vs general triage). Use Glob/Read to discover what is there and load only what applies to this bug. Do not assume all rules apply to all bugs.
Expand Down Expand Up @@ -81,6 +81,10 @@ Always be **brief** and to the point. Do not post long-winded comments, develope

Do **not** post private comments, all developers on the bug need to see the comments.

Source-repo edits (Write/Edit) are allowed so you can prepare and inspect a candidate patch.
Comment thread
suhaibmujahid marked this conversation as resolved.

Test your changes by updating existing tests or writing a new test if needed. If an existing test already covers the issue, you can just run it to verify that it fails before the fix and passes after.
Copy link
Copy Markdown
Collaborator

@marco-c marco-c May 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might want to add instructions to avoid "stupid" tests that Claude often generates, @padenot do you have any tips from your usage on this?


# Additional instructions for this run

{extra_instructions}