Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

rule

Turns a repeated correction into a short project rule with the broken and fixed line, then applies it to existing code.

raphaelsalaja · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add raphaelsalaja/skills --skill rule

About this skill


name: rule description: Turns a repeated correction into a short project rule with the broken and fixed line, then applies it to existing code.

Rule

This skill turns a correction into a written rule. It writes the rule once in the right file, then fixes the code that already breaks it.

Twice is a rule

When the user says "make it a rule", "always", "never" or "remember this", write it down. When they correct the same thing twice, propose a rule. A rule is a pair, short enough to read before every edit.

Following the rules while editing belongs to scope. Reviewing a codebase against all of them runs in audit.

1. Read what exists

Read AGENTS.md, CLAUDE.md and the editor rule folders before acting. Acting against a written rule is rule-read-before-acting.

2. Write the pair

State the rule in one sentence, then the broken line and the line that replaces it. A rule with no example is rule-write-the-pair.

3. Keep it short

One rule is one to three sentences plus its pair. A paragraph of reasoning is rule-keep-it-short.

4. Give it one home

Put the rule in the file that owns its topic. Copying it into a second file is rule-one-home. When a new rule contradicts an old one, replace the old one and say so. Two contradicting rules left side by side is rule-resolve-conflicts.

5. Sweep the code

Search for code that breaks the new rule, fix it and list the files. A rule written with old violations left in place is rule-sweep-existing.

The pair

Every check is a pair. The broken line sits beside the line that replaces it.

RuleBrokenReplacement
rule-read-before-actingA pill button added in a repo whose rules forbid pillsRules read first, rounded button
rule-write-the-pair"Use good casing""Labels take Title Case. Add to library becomes Add to Library"
rule-keep-it-shortA paragraph of reasoningOne sentence and a pair
rule-one-homeOne rule in three filesOne file, the others point at it
rule-resolve-conflicts"Use borders" beside "never use borders"The old rule replaced, the change noted
rule-sweep-existingThe rule added, twelve violations leftThe violations fixed and listed

Reporting

Severity. HIGH is an edit that breaks a written rule, or two rules that contradict. MEDIUM is a rule with no pair, or old violations left after a new rule. LOW is a rule longer than it needs.

Format. One finding per root cause:

file:line - [rule-id] what is wrong

Then a Rule | Count | Severity summary. Block when any HIGH remains, Approve otherwise. Mark every rule file you could not read as Not verified.