What it does
amend-coding-standards changes exactly one rule in your coding standards — add, revise, or retire — and handles all the bookkeeping a hand-edit would forget: routing by the transplant test, deduping against every rule already in the destination doc, writing in the standards style, and regenerating the maps and entry summaries so the routing structure never drifts from the docs. One rule in, bookkeeping handled — it never rewrites more than the rule you brought.
A PR-comment URL works as input: the comment body becomes the rule material and the reviewer’s proposed fix becomes the example.
When to reach for it
- Invocation mode. You invoke this by typing
/amend-coding-standards— the agent won’t reach for it on its own. - Trigger boundary. Reach for it when one rule needs to change — a new review insight, a stale idiom, a rule worded wrong. For producing the whole standards set from review history, use distill-coding-standards instead; for checking code against the rules, use apply-coding-standards.
Prerequisites
An existing standards structure: a CODING_STANDARDS/CODING_STANDARDS.md in the repo (see setup-coding-standards) whose map links lead to the docs the amendment lands in.
Route, then confirm
The transplant test runs on the rule’s substance: concrete paths and domain nouns get neutralized to role names first, and the question is whether the remainder still instructs correctly in a stranger’s repo with the same stack. The verdict is a recommendation, not a decision — one question goes to you carrying the scope reading, the generic-vs-project choice, and the recommendation, and no file is touched until you answer. A rule can also split: a generic core plus a project-specific companion carrying the stripped specifics.
It’s working if
- Exactly one of merge / contradiction-raised / new-bullet happened, and you were told which.
- The folder map and entry summaries match the docs as they now stand.
- The final rule text was quoted back to you, in the standards style.
Where it fits
The maintenance step of the coding-standards chain — the small tool between big distillations: distill-coding-standards produces the rules in bulk, this skill edits them one at a time, and review-with-coding-standards feeds it candidates — legitimate review points no rule covers yet. For the map of the whole set, see ask-eddy.