Skip to content
Skills Library
Programming · Planning

fix

/fix

Use when a bug ticket or GitHub issue should go from report to an approved fix plan — "plan a fix", "fix this issue". Root-causes it via rca, then plans in plan mode with the failing regression test first. Routes to hex-plan instead when the fix is large or moves an interface contract.

Repository
grimoire ↗
Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when a bug ticket or GitHub issue should go from report to an approved fix plan — "plan a fix", "fix this issue". Root-causes it via rca, then plans in plan mode with the failing regression test first. Routes to hex-plan instead when the fix is large or moves an interface contract.

Triggers from the description

plan a fixfix this issue

Arguments

/fix issue-number | url | description
Original author description

Use when a bug ticket or GitHub issue should go from report to an approved fix plan — "plan a fix", "fix this issue". Root-causes it via rca, then plans in plan mode with the failing regression test first. Routes to hex-plan instead when the fix is large or moves an interface contract.

How it works

  1. 1. Root cause
  2. 2. Verdict gate
  3. 3. Escalation gate
  4. 4. Plan
Original SKILL.md headings · 40 lines, 323 words
SKILL.md preview
---
name: fix
description: Use when a bug ticket or GitHub issue should go from report to an approved fix plan — "plan a fix", "fix this issue". Root-causes it via rca, then plans in plan mode with the failing regression test first. Routes to hex-plan instead when the fix is large or moves an interface contract.
user-invocable: true
argument-hint: "issue-number | url | description"
triggers:
  - "plan a fix"
  - "fix issue"
  - "fix this issue"
  - "fix ticket"
---

# Fix — RCA, then a regression-test-first plan

## 1. Root cause

Read [`../rca/SKILL.md`](../rca/SKILL.md) and follow it in full against `$ARGUMENTS`. Do not shortcut its gates — a fix plan built on an unverified cause is the failure this skill exists to prevent.

## 2. Verdict gate

Verdict ≠ `bug` → output the RCA report and stop. No plan.

## 3. Escalation gate

Stop and do **not** enter plan mode when any holds:

- size **L** or **XL** ([`../rca/references/sizing.md`](../rca/references/sizing.md))
- any interface surface is touched (same file, list)
- confidence **low**, or repro **not reproduced** with no observed causal chain

Output the RCA header, the one-line reason, and:

```
## Actions
- Run `/hex-plan <issue>` with this RCA as input   (XL → `/hex-architect` first)
```

## 4. Plan

Call `EnterPlanMode` (load it via `ToolSearch` `select:EnterPlanMode` if deferred). The plan file holds, in order:

1. **RCA header** — the five-line block from the report, plus the causal chain's key `file:line`.
2. **Regression test — first.** Level per `workflow-bugfix.md` Phase 3: acceptance bug → pytest in `test/tests/`; unit bug → inline `#[cfg(test)]` in the faulty module. Name the test, what it asserts (the root cause, not the symptom), and the command that shows it **red on current HEAD** (`task test:parallel --force -- tests/<file>` or `cargo test <filter>`). One per blast-radius site when the sites differ in behaviour.
3. **Fix** — at the root-cause layer; every site from the blast radius covered or explicitly excluded with reason. No drive-by refactor.
4. **Verify** — regression test green, the subsystem gate for the code changed (`task rust:verify`), then `task verify` as the final gate before commit.
5. **Commit** — `fix(<scope>): <user-facing sentence>`, signed off (`git commit -s`); the subject is the changelog line. `Fixes #<n>` in the body.

Then `ExitPlanMode`. After approval, implement per `workflow-bugfix.md` (the `/bugfix` checklist): test red first, then fix, then green. If the fix grows past **M** mid-implementation, stop and re-enter step 3.

$ARGUMENTS

Versions

RepositoryScoreLicence
This page · grimoire-rs/grimoire100Apache-2.0
swingerman/engineer100MIT
Hainrixz/claude-seo-ai100MIT
vanducng/skills100MIT
RemiPelloux/kill-my-idea100MIT
tony/skills100MIT
applelog/nondev-kit100MIT
A7-studio/jobmigo100MIT
koda-ai-studio/agent-bom100Apache-2.0

Database snapshot: 13.11.2026 · package version 53eb04112a69 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 2 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100rca
    Use when a bug ticket, GitHub issue or error report needs a root cause analysis before code is touched — "is this a bug", "why does this fail". Read-only. Gives a verdict (bug or not-a-bug kind), file:line evidence, ruled-out hypotheses, other affected sites, fix direction and…
  • 90fix-issue
    Use when fixing a GitHub issue — reproduce, trace root cause, fix, add regression test
  • 90pb-bug-fix
    Turn a GitHub issue into a tested fix on a branch with an open PR: read the issue as the contract, find the root cause, write the failing test first, fix, prove it, review the diff against the issue, push and open the PR only after GO. Merging stays with pb-ship. Use for "fix…
  • 90fix-issue
    Takes a GitHub issue from description to a verified fix: reads it with gh, reproduces the problem, fixes the root cause with a regression test on its own branch, runs the checks and prepares the commit and PR. Use when the user points to an issue and asks to fix it (/fix-issue…
  • 100fix-issue
    Analyze and fix a GitHub issue for the iam-policy-validator project. Use when the user wants to fix a GitHub issue, resolve a bug report, or implement a feature request from an issue. Triggers on "/fix-issue", "fix issue #42", "resolve this GitHub issue", or "work on issue".
  • 100bug-fix
    Bug-fixing workflow that coordinates diagnosis, test-driven reproduction, root-cause analysis, and targeted fixes. Use when the user wants to fix a bug with thorough investigation and regression testing.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.