Update conventions

Skill eugenelim/agent-ready-repo/packs/governance-extras/.apm/skills/update-conventions

Use this skill when the user wants to change `docs/CONVENTIONS.md` or `docs/CHARTER.md`. Triggers on "let's change the convention for...", "update the rules", "amend the charter", "change our principles". Conventions and charter changes go through RFC review, not direct PR.From its SKILL.md

Install

npx -y skills add eugenelim/agent-ready-repo --skill update-conventions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.4 KB, 277 tokens by cl100k_base, as published. Nobody here has run it

Skill: update-conventions

Edits to docs/CONVENTIONS.md and docs/CHARTER.md are not normal PRs — they change how everyone works in the repo. They go through RFC review.

Procedure

Push back if the user starts editing directly. Conventions changes are high-leverage; they should be deliberated.
Open an RFC instead. Use the new-rfc skill, with the RFC scoped to "change conventions section X to Y". The RFC's Proposal section should contain the specific edited text — the diff, essentially.
After the RFC is accepted, the actual edit to CONVENTIONS.md is a small PR that cites the RFC in the commit footer:
```
docs(conventions): adopt RFC-NNNN — <one-line summary>

Implements RFC-NNNN: <link>
```
Update the RFC's Follow-on artifacts section to point at the merged commit.

Exception

Trivial edits — typo fixes, broken-link fixes, formatting — don't need an RFC. A normal PR is fine. If you're not sure, err toward RFC: the cost of an extra RFC is small; the cost of an unannounced rule change is large.

What ships with it: 2 files

3.5 KB alongside SKILL.md

evals/

eval_queries.json1.8 KB
evals.json1.7 KB