
Fix categories
| Category | What it is | What you do |
|---|---|---|
| Immediate | A small, low-risk change that stops the bleed: a monitor threshold, an alert config tweak, a runbook step. Comes with rationale and any code snippets or CLI commands you need. | Read the steps and run them yourself. Antimetal doesn’t execute commands or change monitors. |
| Comprehensive | A code change that addresses the root cause. Includes a generated diff. | Review the diff, then open a PR from Antimetal or pull the fix into your IDE or coding agent to keep editing. |
Immediate fixes
Open an immediate fix to see the full plan: why the change is needed, then numbered steps with the exact commands to run.
Comprehensive fixes
Before generating a fix, Antimetal reads yourAGENTS.md, CLAUDE.md, and any Cursor or Copilot rules files in the repo, alongside its memory of your system and past incidents. Fixes come back in your code style and follow your team’s conventions.
Antimetal does not run your tests or builds against the fix. Validate the change locally or in CI before merging.


- Create PR opens a pull request on your repo, branching from the default branch. Requires the GitHub integration. Once it’s open, treat it like any other PR: push more commits, rebase, or rewrite the diff.
- Create draft PR does the same as a draft, so reviewers aren’t pinged while you tighten things up. Mark it ready when it’s where you want it.
- Open in Codex / Cursor / Devin / GitHub Copilot hands the fix and its context off directly so you can keep iterating in your editor.
- Copy fix as prompt copies the fix and surrounding context as a prompt you can paste into any IDE or coding agent.
What an Antimetal PR looks like
- The PR is authored by
antimetal[bot], so reviewers can tell at a glance the change came from an agent. - Antimetal tags any matching
CODEOWNERSand also auto-tags engineers who have recently reviewed the impacted code.
![Example Antimetal PR authored by antimetal[bot]](https://mintcdn.com/antimetal-6e0eb43b/k3oVqyCPybUS8nNr/images/fixes/pr-example.png?fit=max&auto=format&n=k3oVqyCPybUS8nNr&q=85&s=e1ad6348d0ceab2152e86f677fca4aa1)
🧪 PR creation is experimental. Engineers are responsible for validating every change before merging. Antimetal will never merge for you.
How to respond to an Antimetal PR
When an Antimetal PR lands in your queue, you have four paths:- Approve and merge if the diff is correct as-is.
- Take it over the line by adding commits, rebasing, or rewriting parts of the diff before merging.
- Request changes if the approach is right but the diff isn’t. Leave inline review comments and add any context you have — feedback on what’s off or what the agent missed helps Antimetal learn.
- Close as not relevant if the underlying issue no longer applies or the agent misread the situation.
What Antimetal will and will not do today
- Will: investigate, propose fixes, generate code changes, open PRs you trigger from the Fixes page (authored as
antimetal[bot]), hand off to coding agents. - Will not: open branches or PRs unprompted, run CLI commands, change monitors or alerts, apply infrastructure changes, run your tests or builds, update the PR based on review feedback, push commits without you, or merge.