skills.rest
phanijapps
phanijappsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

update-conventions

Route CONVENTIONS.md and CHARTER.md changes through an RFC review process.

Updated Jun 29, 2026
Search Tags:#documentation#governance#conventions#process#rfc#charter
One-click install
npx skills add https://github.com/phanijapps/engram --skill update-conventions-phanijapps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-conventions
Source: https://github.com/phanijapps/engram/tree/main/.claude/skills/update-conventions
Command: npx skills add https://github.com/phanijapps/engram --skill update-conventions-phanijapps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents uncoordinated changes to repository-wide rules and principles by enforcing a structured RFC review process for modifications to core documentation.

Core Features & Use Cases

  • RFC Enforcement: Ensures that changes to CONVENTIONS.md or CHARTER.md are deliberated rather than applied via direct, opaque PRs.
  • Standardized Workflow: Guides the user to draft an RFC, obtain consensus, and then perform a small, linked PR to finalize the documentation update.
  • Use Case: When a team decides to switch from standard commits to conventional commits, this skill ensures the change is proposed, discussed, and documented as an RFC before the conventions file is updated.

Quick Start

Trigger this skill by asking to update the rules for our commit message format or amend the charter to include new principles.

Frequently Asked Questions about update-conventions

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

FAQPage Schema
How do I enforce a review process for updating repository conventions?▼

RFC review enforces structured deliberation for modifying CONVENTIONS.md by requiring proposed changes to be drafted, discussed for team consensus, and auditably linked to a follow-on PR before finalizing.

What is the best way to manage charter updates without uncoordinated PRs?▼

The best way to manage charter updates is routing CHARTER.md modifications through an RFC review process, preventing opaque direct PRs by enforcing structured deliberation and team consensus before finalizing policy changes.

Do I need an RFC to change high-leverage governance documentation?▼

Yes, you need an RFC to change high-leverage governance documentation. This skill requires integration with a new-rfc skill to ensure proposed modifications to core files are properly deliberated and linked to follow-on PRs.

How does the RFC process work for switching to conventional commits?▼

The RFC process for switching to conventional commits involves proposing the documentation change, obtaining team consensus through deliberation, and then performing a small, linked PR to finalize the update to the conventions file.

Can I apply direct changes to CONVENTIONS.md using this workflow?▼

No, you cannot apply direct opaque changes to CONVENTIONS.md. This workflow specifically prevents uncoordinated modifications by enforcing a standardized RFC review process for all repository-wide policy updates.

Related Skills

Explore More Software Engineering Skills→
eugenelimeugenelim
15

update-conventions

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

Community
Intermediate
phrazzldphrazzld
13

standup

Aggregate GitHub activity into a Yesterday/Today/Blockers standup report.

Community
Intermediate
KaakatiKaakati
2

technical-rfc

Generates structured RFC documents for architectural and process changes.

Community
Advanced
velcraftingvelcrafting
1

authz-policy

Define and enforce authorization rules for protected actions with deny-by-default behavior.

Community
Advanced