update-conventions

Name: update-conventions
Availability: InStock
Author: eugenelim

Routes changes to repository governance docs through an RFC review process.

15|5|Updated May 4, 2026

Search Tags:#governance #review #conventions #policy #rfc #charter

Ready to run

npx skills add https://github.com/eugenelim/agent-ready-repo --skill update-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-conventions
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/.agents/skills/update-conventions
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill update-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents high-leverage repository rules from changing informally by routing convention and charter edits through deliberate RFC review.

Core Features & Use Cases

RFC-First Governance: Pushes back on direct edits to docs/CONVENTIONS.md and docs/CHARTER.md and opens an RFC instead.
Scoped Change Proposals: Frames the RFC around a specific change and includes the exact edited text in the Proposal section.
Controlled Follow-Through: Plans a small follow-up PR that cites the RFC and updates the RFC's follow-on artifacts after merge.
Practical Exceptions: Treats typo fixes, broken links, and formatting-only changes as normal PRs.

Quick Start

Ask the assistant to route your requested conventions or charter change through an RFC instead of editing the document directly.

Frequently Asked Questions about update-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I require an RFC review for changes to repository conventions?▼

You can route changes to docs/CONVENTIONS.md and docs/CHARTER.md through RFC review by opening a scoped RFC with the proposed diff in the Proposal section, followed by a small PR that cites the RFC and updates its follow-on artifacts.

What repository governance changes require an RFC instead of a direct edit?▼

Repository governance changes that require an RFC include any requests to rename, redefine, expand, or narrow rules, principles, scope, or governance language in docs/CONVENTIONS.md and docs/CHARTER.md, ensuring high-leverage rules avoid informal modification.

Can I fix a typo in docs/CONVENTIONS.md without opening an RFC?▼

Yes, you can fix typos in docs/CONVENTIONS.md without an RFC. Typo fixes, broken links, and formatting-only changes are treated as trivial exceptions and bypass the RFC review process as normal PRs.

How do I structure an RFC for updating a project charter?▼

To structure an RFC for updating a project charter, frame the RFC around the specific change and include the exact edited text in the Proposal section. After merging, plan a small follow-up PR that cites the RFC and updates follow-on artifacts.

Why should repository rules go through an RFC process instead of direct PRs?▼

Repository rules should go through an RFC process to prevent high-leverage rules from changing informally. Routing convention and charter edits through deliberate RFC review ensures changes are scoped, proposed with exact diffs, and properly cited in follow-up PRs.