docs(corrections): place principle parts 4c, 4e and 4f in /corrections:codify

Open Beginner friendly
  • Is something wrong?
#12,716 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Read docs/upstream/cursor-pstack.md first to see the principle-parts check, then open plugins/corrections/skills/codify/actions/note.md (Consent section and opening paragraph) and plugins/corrections/skills/codify/SKILL.md (section 3). Add the three reasoned sentences for parts 4c, 4e and 4f using the wording in the issue's done-when list, and update the pstack check so 4c, 4e and 4f show as placed with their homes and no longer name #7573. Done when all four checkboxes hold.

Written by the indexing model from the issue text.

Description

agent-ready priority: medium status: ready work-class: scoped

Refs #7589

Outcome

Parts 4c, 4e and 4f of principle-encode-lessons-in-structure each become a reasoned sentence in /corrections:codify, and the pstack record lists them as placed. This is #7589's remainder: its nine sub-issues are closed, and these three parts had no owning issue.

Done when

The done-when lines below are copied from #7589's Remainder section as written.

  • Part 4c ("When you catch yourself writing the same instruction a second time") is a reasoned sentence in plugins/corrections/skills/codify/actions/note.md, Consent section: an agent that writes the same instruction or correction a second time appends a note, because a second occurrence shows a prose rule did not hold.
  • Part 4e ("decide if it's a one-off or a pattern. Route it ... Close the loop: don't just record; apply now or create a concrete todo") is a reasoned sentence in plugins/corrections/skills/codify/SKILL.md, section 3 (Place the lesson by scope): a one-off stays a note row, a recurring mistake gets a check, a mistake that holds for every repository becomes a team standard, and recording a lesson is not the end: it ends in a proposed check, a placed rule or a filed work item, because a lesson that is only recorded is not acted on. Codify still proposes and never builds a rung.
  • Part 4f ("Acknowledging without recording", "Recording without routing") is a reasoned sentence in plugins/corrections/skills/codify/actions/note.md, opening paragraph: a correction the agent only acknowledges is lost when the session ends, and a note that group never routes to /corrections:codify changes nothing.
  • docs/upstream/cursor-pstack.md's principle-parts check lists 4c, 4e and 4f as placed, with their homes, and no longer names #7573 as their owner.

Notes

Drafted by the issue-triage session. Agent choice, not an owner answer. The quoted part text is from the cursor/plugins version decision 58 mapped (00b14f1df3), restated in #7589, so the work needs nothing outside this repository.

Related

  • #7589 (parent), #12155, #9161, #7573.
Dominant language
Shell
Stars
22
Forks
2
Avg merge
1h 29m
Merged PRs (30d)
895

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from melodic-software/claude-code-plugins

All issues in melodic-software/claude-code-plugins

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.