Skip to content
Skills Library
AI & agents · Automation

correction

/correction

Turn a correction the user made to an agent into a Suggested task card that starts a fix session in one click, list the corrections filed as issues before the card, write a handoff brief, or land the fix in this session with the fix playbook. Use when the user types /correction, /correction fix, says "file this as a correction", or asks to show the open corrections.

Licence
MIT
Last repository change
27.10.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
14
Scripts
10
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 10 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/correction_filing.py, scripts/correction_filing_constants/__init__.py, scripts/correction_filing_constants/config/__init__.py, scripts/correction_filing_constants/config/constants.py, scripts/correction_task_card.py, scripts/correction_task_card_constants/__init__.py, scripts/correction_task_card_constants/config/__init__.py, scripts/correction_task_card_constants/config/constants.py, scri

What it does and when to use it

Turn a correction the user made to an agent into a Suggested task card that starts a fix session in one click, list the corrections filed as issues before the card, write a handoff brief, or land the fix in this session with the fix playbook. Use when the user types /correction, /correction fix, says "file this as a correction", or asks to show the open corrections.

Triggers from the description

file this as a correction

Arguments

/correction [fix] <what the agent got wrong, in the user's words>
Original author description

Turn a correction the user made to an agent into a Suggested task card that starts a fix session in one click, list the corrections filed as issues before the card, write a handoff brief, or land the fix in this session with the fix playbook. Use when the user types /correction, /correction fix, says "file this as a correction", or asks to show the open corrections.

How it works

  1. Hand it off
  2. List them
  3. Brief
  4. Playbooks
  5. Layout
Original SKILL.md headings · 60 lines, 554 words
SKILL.md preview
---
name: correction
description: Turn a correction the user made to an agent into a Suggested task card that starts a fix session in one click, list the corrections filed as issues before the card, write a handoff brief, or land the fix in this session with the fix playbook. Use when the user types /correction, /correction fix, says "file this as a correction", or asks to show the open corrections.
argument-hint: "[fix] <what the agent got wrong, in the user's words>"
---

# /correction

The user corrected an agent and wants the fix to stick. By default the correction becomes a Suggested task card, and the user starts the fix session from it in one click. No issue is filed. When `$ARGUMENTS` starts with the word `fix`, this session lands the fix itself: write the brief, then follow the fix playbook.

## Hand it off

Use this for `/correction <text>` and "file this as a correction: <text>".

1. Write the brief below, then build the card from it with [`scripts/correction_task_card.py`](scripts/correction_task_card.py). Pipe one JSON object in a quoted heredoc: `title` starts with a verb and stays under 60 characters, `tldr` is one plain sentence, `brief` is the brief block text, and `files` lists the repository-relative paths the brief names.
   ```bash
   python "${CLAUDE_SKILL_DIR}/scripts/correction_task_card.py" <<'CARD'
   {"title": "<verb first>", "tldr": "<one sentence>", "brief": "<brief block, newlines as \n>", "files": ["<repo-relative path>"]}
   CARD
   ```

2. When the session has `mcp__ccd_session__spawn_task`, call it with the `title`, `tldr`, and `prompt` the script prints. Reply with the card title.
3. Without that tool, run the script again with `--prompt-only` and print its output in one fenced `text` block as the handoff brief.

## List them

For "show the open corrections", run `python "${CLAUDE_SKILL_DIR}/scripts/correction_filing.py" list` and print its lines. It lists the issues filed before the card replaced filing, and the issues the correction flag mod still files.

## Brief

Print one fenced `text` block. Fill the fields from this session: the transcript, the files and pull requests it touched, and the messages it sent. Write `unknown` for a field the session does not settle.

```text
Correction: <$ARGUMENTS word for word, minus a leading fix>
Asked: <what the user asked for, quoted where a message carries it>
Agent did: <what the agent did, with the reply, file, or command that shows it>
Corrected to: <what the user wanted instead, or the fix already made>
Where: <repository, branch or pull request, files, tool, or thread>
Evidence: <file:line, log line, or quoted message that shows the miss>
Repeat: <yes, with the earlier time it happened | no | unknown>
```

Keep each field to one or two lines. Leave out the layer and the fix design; the intake or the fix playbook decides those.

## Playbooks

| Mode | What follows the brief |
|---|---|
| Hand off, the default | The task card, or the handoff brief when `spawn_task` is absent. |
| `fix` | Read [`playbooks/fix.md`](playbooks/fix.md) right after the brief, and run its steps from step 2. |

## Layout

| File | What it holds |
|---|---|
| `SKILL.md` | The handoff, the listing, the brief, and the playbook index |
| `playbooks/fix.md` | The steps that land one correction as a control and a pull request in this session |
| `scripts/correction_task_card.py` | Builds the `spawn_task` title, tldr, and standalone prompt from the brief and the fix playbook |
| `scripts/correction_task_card_constants/config/constants.py` | Card field rules and the prompt template |
| `scripts/test_correction_task_card.py` | Behavior tests for the card against the shipped fix playbook |
| `scripts/correction_filing.py` | Lists the open correction issues, and files one for the correction flag mod |
| `scripts/correction_filing_constants/config/constants.py` | Config keys, issue shape, and redaction patterns |
| `scripts/test_correction_filing.py` | Behavior tests with a stand-in `gh` |
| `references/filing.md` | Config file, issue shape, dedupe, and commands |
Files in this package (14)
  • SKILL.md 4 KB
  • playbooks/fix.md 2 KB
  • references/filing.md 2 KB
  • scripts/correction_filing.py 11 KB
  • scripts/correction_task_card.py 6 KB
  • scripts/pytest.ini 1 KB
  • scripts/test_correction_filing.py 7 KB
  • scripts/test_correction_task_card.py 5 KB
  • scripts/correction_filing_constants/__init__.py 1 KB
  • scripts/correction_filing_constants/config/__init__.py 1 KB
  • scripts/correction_filing_constants/config/constants.py 2 KB
  • scripts/correction_task_card_constants/__init__.py 1 KB
  • scripts/correction_task_card_constants/config/__init__.py 1 KB
  • scripts/correction_task_card_constants/config/constants.py 1 KB

Versions

The database has no other skills named correction.

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

Downloads in the last 30 days: 0 · ranking

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

Similar skills

  • 90correction-to-skill
    Turns a correction from the user into a dated rule in the skill, agent or instruction file that caused the mistake, in the same session, and says where it went. Use when the user says "that's wrong", "not what I asked", "I told you before", "why didn't you", "remember this",…
  • 100corrections-audit
    Use to analyze correction trends, surface recurring patterns, and graduate repeat corrections to guardrails or anti-patterns.
  • 100common-learning-log
    Append a learning entry to AGENTS_LEARNING.md when an AI agent makes a mistake. Auto-activates after a pre-write audit auto-fix, a retrospective correction loop, or a mid-session user correction. Use when: mistake, wrong, correction, my bad, agent error, learning log.
  • 90running-retrospectives
    Use when the same correction keeps recurring across multiple work sessions, or at the end of a session to harvest recurring project-specific user feedback into durable memory. Not for one-off corrections — a correction seen in only one session is not yet eligible.
  • 100common-learning-log
    Append a learning entry to AGENTS_LEARNING.md when an AI agent makes a mistake. Auto-activates after a pre-write audit auto-fix, a retrospective correction loop, or a mid-session user correction. Use when: mistake, wrong, correction, my bad, agent error, learning log.
  • 100feedback-loop
    When the user corrects earlier output, records the correction for the repository, fixes the files, has an evaluator that edits nothing judge the fix against stated criteria, and repeats fix and review until every criterion passes, then keeps the lesson as a check for that file…

Feedback and reports

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