Codex Heal
Use this skill when:
- monitor has identified a bounded critical/high issue
- you want an isolated remediation branch or worktree
- you need a separate fixing agent from the reporting agent
Goal
Take a prioritized issue queue and convert it into a verified branch, not a silent background mutation.
Non-negotiable rules
- Never modify
maindirectly. - Prefer a dedicated branch or worktree per heal run.
- Keep fixes surgical.
- Run quality gates and relevant tests.
- Do not auto-merge.
- If the issue is not bounded, stop and write back to Linear instead.
Input requirements
Each issue passed into heal should include:
- title
- severity
- source system
- problem statement
- relevant file/service area
- suggested owner or fix lane
Workflow
- Confirm working tree state is safe.
- Create a remediation branch or worktree.
- Group issues by technical lane:
- backend
- frontend
- infra/deploy
- security
- Fix one group at a time.
- Run gates:
- typecheck
- lint
- build
- targeted tests
- Re-check the original failure signal where possible.
- Summarize:
- fixed
- not fixed
- unverified
- residual risk
Confidence model
High confidence:
- original problem reproduced or clearly understood
- change set is narrow
- gates passed
- signal cleared or likely cleared
Low confidence:
- issue not reproducible
- broad changes required
- incomplete verification
- additional failures introduced
Output contract
Every heal run should end with:
- branch/worktree name
- what changed
- gates run
- confidence
- recommended next human action