encero-systems/incan / .agents/skills/fix
fix
VerifiedFix actionable in-scope findings in the current Incan worktree, usually after /review. Use when the user asks to fix review findings, clean up reported issues, apply in-scope review feedback, or says /fix.
Fix — Incan Compiler
Purpose
/fix is the repair half of the review workflow. It consumes concrete findings from /review or obvious unresolved worktree issues and fixes them directly when they are in scope and safe.
The primary source of truth is the persistent report in the current worktree:
.agents/state/review-report.md
Use /fix when:
/reviewalready identified blockers or warnings,- the user says "fix the findings",
- the user wants review cleanup without a fresh diagnostic pass.
Do not use /fix as a substitute for first-pass diagnosis when the problem is still unclear. Use /review first.
/fix is different from /review: it should consume the current report, not wipe it. If the report is stale or obviously belongs to a previous run, rerun /review instead of trying to repair against bad state.
Workflow
- Start from the current dirty worktree and the concrete findings already on record from
/review, inline review comments, or the user's instructions. - Read
.agents/state/review-report.mdfirst when it exists. - For orchestrated reviews, treat
## Findingsas the default task list. - For generic single-review reports, fall back to
## Filesonly if there is no top-level## Findingslist. - Fix only findings that are:
- in scope,
- safe without extra user confirmation,
- concrete enough to act on.
- Do not widen scope. Avoid opportunistic refactors beyond what is needed to resolve the findings cleanly.
- Update
.agents/state/review-report.mdas findings move betweenopen,fixed, andblocked. - Append short timestamped entries to
## Activityas you work. Log each major action instead of relying on a final prose recap. - After edits, run
make fmt. - Run the narrowest relevant verification for the fixes you made.
- Run
make pre-commit. - If
make pre-commitfails for reasons unrelated to your fixes, keep the local fixes and report the failure as residual risk in the report file. - If findings remain unresolved, classify each as one of:
- out of scope,
- risky without user confirmation,
- external blocker,
- separate compiler bug.
- Preserve findings even when they are non-blocking or design-oriented.
design-tension,maintainability, and docs drift are still findings; they may simply move to a lower-priority fix queue instead of being dropped.
Fixing rules
- Preserve the user's worktree. Never revert unrelated changes.
- Prefer small direct edits over broad rewrites.
- Keep docs and code aligned. If you fix behavior, update user-facing docs that claim the old behavior. If behavior is out of scope, correct the docs instead of inventing implementation.
- For Rust prose comments, write natural paragraphs and let
make fmtwrap them. Do not manually chop prose into short lines. - For Markdown, keep prose as natural paragraphs. Do not introduce short-prosed or mechanically chopped text.
- Do not fix boundary bugs with local-only coverage. If a finding involves import, reexport/facade, package consumer, dependency-owned type, test batch, vocab/desugarer, formatter, generated Rust, Rust metadata, or downstream behavior, add the relevant boundary coverage or document why that boundary is impossible for this fix.
- Do not add a new split-brain workaround while fixing a split-brain bug. Prefer moving the decision into the canonical planner, metadata surface, registry, or shared helper that all relevant paths already consume.
Verification
/fix should usually run:
make fmt- narrow relevant tests or checks
make pre-commit
If make pre-commit fails because of unrelated sandbox or network issues, say so explicitly in .agents/state/review-report.md. That does not justify leaving local findings unfixed.
The report must remain a structured artifact. Do not replace it with a narrative summary. If ## Activity is missing, repair the report before you finish. For orchestrated runs, the canonical report should stay thin and findings-driven; do not recreate a giant per-file checklist there.
When consuming an orchestrated report, update:
## Findings## Disagreementswhen relevant## Verification
Do not invent new findings unless the edit work uncovers a tightly related issue needed to finish the requested fix cleanly. Classification on findings is for handling, not suppression.
Output format
Produce a concise report with:
## Fix — <subject / branch / files>
### Fixed
<item> — <file>:<line> — <what changed>
### Verification
<command> — <result>
### Residual risk
<anything still unresolved, with classification>
If nothing needed fixing, say so directly.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |