claude-dev-env 8.68.4 → 8.69.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1,19 +1,19 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: correction
|
|
3
|
-
description: Turn a correction the user just made into a short handoff brief they paste into a corrections intake. Use when the user types /correction followed by what the agent got wrong.
|
|
4
|
-
argument-hint: "<what the agent got wrong, in the user's words>"
|
|
3
|
+
description: Turn a correction the user just made into a short handoff brief they paste into a corrections intake, or land the fix in this session with the fix playbook. Use when the user types /correction followed by what the agent got wrong, or /correction fix to land the fix here.
|
|
4
|
+
argument-hint: "[fix] <what the agent got wrong, in the user's words>"
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# /correction
|
|
8
8
|
|
|
9
|
-
The user corrected an agent and wants the fix to stick. Write one brief
|
|
9
|
+
The user corrected an agent and wants the fix to stick. Write one brief that records the correction. By default the user pastes it into the place that turns corrections into lasting fixes. When `$ARGUMENTS` starts with the word `fix`, this session lands the fix itself.
|
|
10
10
|
|
|
11
|
-
`$ARGUMENTS` is the user's statement of the correction. Fill the other fields from this session: the transcript, the files and pull requests it touched, and the messages it sent. When the session does not settle a field, write `unknown` there.
|
|
11
|
+
`$ARGUMENTS` is the user's statement of the correction, after a leading `fix` when one is present. Fill the other fields from this session: the transcript, the files and pull requests it touched, and the messages it sent. When the session does not settle a field, write `unknown` there.
|
|
12
12
|
|
|
13
|
-
Print the brief as one fenced `text` block
|
|
13
|
+
Print the brief as one fenced `text` block:
|
|
14
14
|
|
|
15
15
|
```text
|
|
16
|
-
Correction: <$ARGUMENTS
|
|
16
|
+
Correction: <$ARGUMENTS word for word, minus a leading fix>
|
|
17
17
|
Asked: <what the user asked for, quoted where a message carries it>
|
|
18
18
|
Agent did: <what the agent did, with the reply, file, or command that shows it>
|
|
19
19
|
Corrected to: <what the user wanted instead, or the fix already made>
|
|
@@ -22,4 +22,18 @@ Evidence: <file:line, log line, or quoted message that shows the miss>
|
|
|
22
22
|
Repeat: <yes, with the earlier time it happened | no | unknown>
|
|
23
23
|
```
|
|
24
24
|
|
|
25
|
-
Keep each field to one or two lines. Leave out the layer and the fix design; the intake decides those.
|
|
25
|
+
Keep each field to one or two lines. Leave out the layer and the fix design; the intake or the fix playbook decides those.
|
|
26
|
+
|
|
27
|
+
## Playbooks
|
|
28
|
+
|
|
29
|
+
| Mode | What follows the brief |
|
|
30
|
+
|---|---|
|
|
31
|
+
| Hand off, the default | Nothing. The brief is the whole reply. |
|
|
32
|
+
| `fix` | Read [`playbooks/fix.md`](playbooks/fix.md) right after the brief, and run its steps from step 2. |
|
|
33
|
+
|
|
34
|
+
## Layout
|
|
35
|
+
|
|
36
|
+
| File | What it holds |
|
|
37
|
+
|---|---|
|
|
38
|
+
| `SKILL.md` | The brief and the playbook index |
|
|
39
|
+
| `playbooks/fix.md` | The steps that land one correction as a control and a pull request in this session |
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
# Fix
|
|
2
|
+
|
|
3
|
+
Use this playbook when this session lands the fix for the correction itself. One correction gets one control and one pull request.
|
|
4
|
+
|
|
5
|
+
1. Write the brief from [`../SKILL.md`](../SKILL.md) first. It is the record every later step reads.
|
|
6
|
+
2. When pstack is loaded, invoke `/pstack:poteto-mode`, then `/correct`. Point `/correct` at the brief's mistake alone, and skip its sweep of the whole repository.
|
|
7
|
+
3. Read the correction instructions of the repository the mistake happened in. Open each `AGENTS.md` or `CLAUDE.md` index line that names corrections, and any intake note it points to. Where they name the target repository, the proof, or the run route, they win over this playbook.
|
|
8
|
+
4. Search for an existing control: a rule, hook, lint, test, or skill that already names this mistake. A control that exists and still let the mistake through makes this a repeat.
|
|
9
|
+
5. Choose the layer with [`correction-lens.md`](../../../../docs/rule-guides/correction-lens.md). When `Repeat` is `yes`, or step 4 found a control, go one layer above the one that failed.
|
|
10
|
+
6. Land the control in the repository whose code, CI, or agents it guards, per the guide's "Where the control lands" section. When that repository is not in this session, add it. When it cannot be added, print the brief, name the missing repository, and stop.
|
|
11
|
+
7. Prove the control. Show it fail on the mistake from the brief's `Evidence` line, then pass with the change, per [`falsify-before-green.md`](../../../../rules/falsify-before-green.md) and [`proof-before-pull-request.md`](../../../../rules/proof-before-pull-request.md). Without that proof, open no pull request.
|
|
12
|
+
8. Open the pull request through `pr-lifecycle`. Put the brief, the layer, and both proof results in the body.
|
|
13
|
+
|
|
14
|
+
**Reply:** the layer chosen, why each higher layer cannot hold the lesson, and the pull request link.
|