Skip to content

Fix tiers ​

Every fix falls in a cell: the recipe that made it (or Claude), the provider, and the kind of change. Each cell has a tier that decides what SHAPI does with a verified fix:

  • REVIEW: the fix PR opens as a draft, for a person to check. Every cell starts here.
  • AUTO: the fix PR opens ready for review. A cell earns it only on the benchmark: 5 instances fixed with no edit outside the predicted lines, and no instance in the run that the fix failed.
  • ALERT: no fix PR. The change is listed on the Dashboard issue as a manual fix.

The tiers come from data, never from hand:

  • Authentication and scope changes stay at REVIEW, whatever the benchmark says.
  • Merge outcomes lower a tier. When three or more of your fix PRs in a cell were closed without merging, more than were merged, that cell drops one tier for your account: AUTO to REVIEW, REVIEW to ALERT.
  • SHAPI can demote a cell, with a reason shown below. A demotion can only lower a tier.

Every fix PR shows its tier next to its size and confidence.

The registry ​

From the benchmark run on APIBreak-Replay v0, SHAPI 0.3.1, 2026-10-30: 0 cells at AUTO, 33 at REVIEW, 0 at ALERT.

RecipeProviderChangeTierBenchmarkWhy
apply-fixhubspotfield-renameREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
apply-fixhubspotversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
apply-fixmeta-graphversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
apply-fixquickbooksversion-sunsetREVIEW0 fixed, 2 not
Instances
❌ quickbooks-minorversion-below-75__hfscdogg__outgrow
❌ quickbooks-minorversion-below-75__RCOLKITT__AccountingQB-MCP
2 benchmark instances not fixed cleanly
apply-fixshopifyversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
apply-fixstripeenum-addedREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmanthropicstatus-codeREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmanthropicversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmgoogle-geminiversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmgoogleversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmhubspotfield-renameREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmhubspotversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmmeta-graphfield-renameREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmmeta-graphversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmopenaiversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmquickbooksauthREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmquickbooksfield-renameREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmsalesforceauthREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmshopifyauthREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmshopifyversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmslackversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmtwilioenum-addedREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmtwiliofield-renameREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmtwiliorequired-fieldREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmtwilioversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmxenum-addedREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmxscope-changeREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmxeroenum-addedREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmxerorequired-fieldREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmxeroscope-changeREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmxerostatus-codeREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
llmxeroversion-sunsetREVIEW0 fixed, 0 not 0 of the 5 benchmark passes AUTO needs
status-code-accept-setgithubstatus-codeREVIEW0 fixed, 2 not
Instances
❌ github-workflow-dispatch-204-to-200__vincentng295__gemini_fbchat
❌ github-workflow-dispatch-204-to-200__pyzz58__gpt-recommendations
2 benchmark instances not fixed cleanly

The benchmark and its instances are in packages/bench; the registry is packages/core/tiers.json, rebuilt from the latest run.