Skip to main content
Auto-fix creates a pull request for a qualifying error group after a completed diagnosis selects the remediate disposition. Diagnosis and remediation share one cycle key, but remain distinct stages: diagnosis is read-only and short-lived; remediation may prepare code.

​
Typical flow

  1. Squasher receives an error and produces an evidence-backed diagnosis.
  2. The diagnosis either requests remediation, asks for a human, or records that no safe fix exists.
  3. For remediate, project policy and repository settings are checked deterministically.
  4. Squasher prepares a candidate patch, verifies it, and opens a pull request for review.
  5. The PR result is sent to configured Slack or webhook review destinations.
  • Connect GitHub.
  • Add a review channel with Slack if your team wants notifications.
  • Pair with Linear if you want issue tracking alongside the PR.

​
Notes

  • Auto-fix is review-oriented. Your team decides whether and when to merge.
  • Better error context generally leads to better candidate fixes.
  • Squasher records terminal cycles, safe refusals, PR creation, tests, verification, and result delivery against the prompt and model version that produced them.

​
Agent handoff

Use this prompt when a coding agent is deciding whether to start a fix run:
Agents can list and inspect run history with the Agent Runs API, squasher agent-runs ..., or MCP Code Mode after search("agentRuns"). Creating a fix run is a write action and should be confirmed by the user.