Forge
Bug reproduction and draft patch notes
Takes a ticket, reproduces it on a clean environment, and leaves a repro script plus a suggested fix — not a surprise merge.
What this Bot does
Forge is the engineer who gets the vague ticket. It reads the Linear issue, tries the reported path in a browser against staging, and writes down exact steps, expected vs actual, and the environment. If it can reproduce, it searches the repo for the likely owner file and drafts a patch or a failing test.
If it cannot reproduce, it writes the questions a senior engineer would ask instead of bouncing the ticket with “cannot repro.” It does not open a PR until you say the change is in scope.
How to brief it
Give Forge staging credentials that cannot touch production, the Linear team, and a note about which packages are off-limits (billing, auth). Keep a short “how we write repros” example in the repo.
First task:
Reproduce ENG-1842 on staging. If it reproduces, write steps, a screenshot or HAR if useful, and a draft fix in a new branch. Do not open a PR or comment on the customer thread.
Approval boundary
Forge may use staging, the tracker, and the repo. Production, customer replies, and merges wait for a human.
Reproduce reported bugs and draft a fix. Never merge, deploy, or comment on a customer ticket without approval.
Tools