Heal Blade PR

Arguments

• PR: Link / Number of the PR to heal

Steps

1. Diagnose

Spawn the pr-sanity-critique subagent to identify all issues:

subagent_type: pr-sanity-critique
prompt: "PR_NUMBER={PR_NUMBER}"

2. Fix

Checkout the PR branch and fix each reported issue:

gh pr checkout {PR_NUMBER} --repo razorpay/blade

• Failing CI: investigate with gh run view --job {JOB_ID} --repo razorpay/blade, then fix the root cause (code, tests, config)
• Missing changeset: create the .changeset file with appropriate bump type — only if the PR contains actual source code changes. Skip changeset creation for PRs with purely test file changes (e.g. *.test.ts, *.spec.tsx) or documentation-only changes (e.g. *.md, docs/).
• Any other issue: follow the critique's suggestion

For test or lint failures, verify the fix locally by re-running the failing check before committing.

3. Handle Non-Fixable Issues

If any issue cannot be fixed (infra outage, external service downtime, flaky environment), post a comment:

gh pr comment {PR_NUMBER} --repo razorpay/blade --body ":sparkles: Agentic PR Healer :sparkles:

**Could not auto-fix the following issues:**

{DESCRIPTION}

These require manual intervention."

4. Push

git add -A && git diff --cached --quiet || (git commit -m "fix: auto-heal PR via Slash PR Healer" && git push)