← ClaudeAtlas

rules-stocktakelisted

Audit ~/.claude/rules (always-loaded behavioral rules) for residency cost, staleness, redundancy, broken See-skill pointers, and substrate absorption, assigning Keep/Improve/Update/Merge/Demote-to-skill/Dissolve/Retire verdicts. Use when the user says "audit my rules", "rules stocktake", "which rules should be demoted or dissolved", 「rules が肥大化してきた」「ルールを棚卸しして」, or when the model generation changed and over-constraints written for the previous one may now be net-negative (「新しいモデルに合わせて rules を見直したい」「rightsize したい」). NOT for — skill quality → skill-stocktake; promoting skill patterns INTO rules → rules-distill (this is its inverse); runtime compliance → skill-comply; whole-config GC → config-gc.
shimo4228/claude-harness · ★ 2 · AI & Automation · score 81
Install: claude install-skill shimo4228/claude-harness
# rules-stocktake — Rules Quality Audit Evaluate every rule file under `~/.claude/rules/` **holistically, all in one context**, and assign each a verdict: `Keep / Improve / Update / Merge / Demote to skill / Dissolve / Retire`. The audit unit is the file; the cost unit is the **line** — rules load into every session unconditionally, so each line is a per-session token tax plus instruction dilution. > Design note: this is skill-stocktake's sibling with the cost model inverted. A skill's > cost is trigger pollution (it fires probabilistically and degrades selection); a rule's > cost is **residency** (it loads always, whether or not it changes behavior). So there is > no usage axis — nothing measures "rule invocations", and the concept doesn't apply to > unconditional loading. The replacements are static: residency density (is each line worth > reading every session?) and substrate absorption (does the harness or the conversation > already do this without the rule?). > Design note 2: unlike skill-stocktake, this skill **does** apply approved Improve/Update/ > Merge edits itself instead of handing off. There is no improvement-engine skill for rules > (skill-creator's counterpart doesn't exist), and rule files average ~60 lines — delegation > would be overengineering. The handoff exception is Demote (creating a new skill is > skill-creator's job). ## Modes (`$ARGUMENTS`) | Argument | Behavior | |----------|----------| | none / `full` | Read and evaluate every rule (default) |