The skill-upkeep hint now includes explicit instructions to fold user corrections back into the driving project skill file, so the next session inherits the fix.
Details
- The guidance is injected whenever Claude saves a
feedback-type memory for a correction that concerns a repeatable step: verifying changes, committing, opening a PR, or running a project skill - The instruction text (constant
KQr) directs Claude to also edit the corresponding.claude/skills/<name>/SKILL.mdfile with a terse, general version of the same correction — so the fix is baked into the skill rather than only stored as a private memory - Claude is told to edit existing skill files rather than creating new ones, because a new project skill shadows a same-named built-in skill by that name
- One explicit exception: if the correction concerns how to verify changes in the current repo and
.claude/skills/verify/SKILL.mddoes not yet exist, Claude should create it
Evidence
Constant KQr (search for "When you save a \feedback\ memory because the user corrected how you ran a repeatable step")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.