How do I install the Repo Propagating Rules skill?

Run npx skillmds add wahidyankf/repo-propagating-rules in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Repo Propagating Rules safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Repo Propagating Rules?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Repo Propagating Rules free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Repo Propagating Rules?

wahidyankf (@wahidyankf) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Repo Propagating Rules by wahidyankf

Name: Repo Propagating Rules
Rating: 4.666666666666667 (3 reviews)
Author: wahidyankf

Repo Propagating Rules

Run the rules-propagation workflow whenever a repository rule is being created, updated, superseded, or deleted. TRIGGERS on "add rule", "new rule", "update the rule", "change the convention", "adjust the rule", "delete that rule", "make it a rule that…", "from now on we should…", "we should always/never…", or any request that would edit repo-governance/, AGENTS.md, CLAUDE.md, an agent or skill definition, repo-config.yml, a hook, or a CI workflow. Load it BEFORE editing any of those surfaces, not after.

wahidyankf 5b40ff4 2 files · 3.5 KB Updated Sep 10, 2026

File contents

Propagating Repository Rules

Rule work does not go in through an ad-hoc edit. It goes through rules-propagation, which exists because placing a rule badly is invisible at review time and expensive later.

Recognising Rule Work

The phrasing varies more than the intent does. All of these are rule work:

Named: "add rule", "update the rule", "change the convention", "delete that rule".
Unnamed: "from now on…", "we should always…", "never do X again", "make sure that before Y we do Z". A standing obligation stated in prose is a rule whether or not the word appears.
Implied by target: any edit to governance prose, the instruction surfaces, an agent or skill definition, the machine-readable declarations, the enforcement wiring, or the language style guides.

A one-off instruction for the current task is not rule work. The test is whether the obligation outlives the work that prompted it.

What Running It Means

Ten steps, summarised: normalize the rule until it is falsifiable both ways; classify its subject, audience, vendor-neutrality, and layer; scan for contradictions and apply layer-aware precedence before writing anything; place it on the narrowest surface that binds, evicting from the instruction surface if it is admitted there; tidy every other surface stating its subject; record one of three enforcement dispositions; verify; deliver.

Read the workflow rather than working from this summary — the steps carry conditions this Skill deliberately does not restate.

Do Not

Do not edit a rule surface first and reconcile it afterwards. The conflict scan is a pre-write step because a contradiction found after the write often means the wrong rule was edited.
Do not finish Step 6 without classifying every subject-scoped rule and discoverability surface as keep, amend, merge, delete, relocate, or supersede. Merge or delete only after every distinct obligation and necessary discoverability path survives at the canonical home; a kept duplicate needs a rationale.
Do not soften an unfalsifiable rule into "guidance" so it can be written. That is a halt.
Do not raise a word budget to make a rule fit.

repo-understanding-shared-vocabulary — whether a given file is a repo rule at all.
Repo Rules — Membership Test.

---name: repo-propagating-rulesdescription: Run the rules-propagation workflow whenever a repository rule is being created, updated, superseded, or deleted. TRIGGERS on "add rule", "new rule", "update the rule", "change the convention", "adjust the rule", "delete that rule", "make it a rule that…", "from now on we should…", "we should always/never…", or any request that would edit repo-governance/, AGENTS.md, CLAUDE.md, an agent or skill definition, repo-config.yml, a hook, or a CI workflow. Load it BEFORE editing any of those surfaces, not after.---# Propagating Repository RulesRule work does not go in through an ad-hoc edit. It goes through[rules-propagation](../../../repo-governance/workflows/rules/rules-propagation.md), whichexists because placing a rule badly is invisible at review time and expensive later.## Recognising Rule WorkThe phrasing varies more than the intent does. All of these are rule work:- Named: "add rule", "update the rule", "change the convention", "delete that rule".- Unnamed: "from now on…", "we should always…", "never do X again", "make sure that before Y we do Z". A standing obligation stated in prose is a rule whether or not the word appears.- Implied by target: any edit to governance prose, the instruction surfaces, an agent or skill definition, the machine-readable declarations, the enforcement wiring, or the language style guides.A one-off instruction for the current task is **not** rule work. The test is whether theobligation outlives the work that prompted it.## What Running It MeansTen steps, summarised: normalize the rule until it is falsifiable both ways; classify its subject,audience, vendor-neutrality, and layer; scan for contradictions and apply layer-aware precedencebefore writing anything; place it on the narrowest surface that binds, evicting from theinstruction surface if it is admitted there; tidy every other surface stating its subject; recordone of three enforcement dispositions; verify; deliver.Read the workflow rather than working from this summary — the steps carry conditions this Skilldeliberately does not restate.## Do Not- Do not edit a rule surface first and reconcile it afterwards. The conflict scan is a **pre**-write step because a contradiction found after the write often means the wrong rule was edited.- Do not finish Step 6 without classifying every subject-scoped rule and discoverability surface as keep, amend, merge, delete, relocate, or supersede. Merge or delete only after every distinct obligation and necessary discoverability path survives at the canonical home; a kept duplicate needs a rationale.- Do not soften an unfalsifiable rule into "guidance" so it can be written. That is a halt.- Do not raise a word budget to make a rule fit.## Related- `repo-understanding-shared-vocabulary` — whether a given file is a repo rule at all.- [Repo Rules — Membership Test](../../../repo-governance/glossary/repo-rules-membership-test.md).

Frequently asked questions