Awesome-omni-skill maintain-project-rules

Audit and maintain project rules in .cursor/rules/. Use when auditing project rules, checking prefix convention, syncing doc/rules.md, or when the user asks about .cursor/rules or prefix convention.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/devops/maintain-project-rules" ~/.claude/skills/diegosouzapw-awesome-omni-skill-maintain-project-rules && rm -rf "$T"

manifest: skills/devops/maintain-project-rules/SKILL.md

source content

maintain-project-rules

Activation gate

Use if:

User asks to audit or maintain project rules, check prefix convention, or sync doc/rules.md.
Context involves
```
.cursor/rules/
```
, rule files (
```
.mdc
```
), or conventions from cursor-rules-principles / retro.

Source of truth

cursor-rules-principles.md (in repo or ~/.cursor) – prefix table 000–500, general principles. See reference.md for full prefix table.
commands/retro.md (PROJECT RULES section) – prefixes 000/050/100/200/900, flat .mdc, no subfolders in rules.

Procedure

Resolve paths
- PROJECT_ROOT:
```
git rev-parse --show-toplevel
```
- PROJECT_CURSOR_DIR:
```
${PROJECT_ROOT}/.cursor
```
- PROJECT_RULES_DIR:
```
${PROJECT_CURSOR_DIR}/rules
```
- If PROJECT_RULES_DIR does not exist, report "No .cursor/rules in this repo" and stop.
Audit
- List all
```
*.mdc
```
  in PROJECT_RULES_DIR (flat; no subfolders per convention).
- For each file: name, prefix vs principles/retro, frontmatter (
```
description
```
  ,
```
alwaysApply
```
  ,
```
globs
```
  ), line count (~<50 preferred), overlap with other rules (duplicate or near-duplicate content).
- Flag: missing prefix, wrong prefix slot, missing/invalid frontmatter, oversized file, duplicate content.
Proposals
- RENAME: file without numeric prefix → suggest prefix from reference.md / retro.
- MERGE: two or more rules with overlapping scope → suggest target file and sections.
- DELETE: only with clear justification (obsolete, fully merged); do not execute without user confirmation.
- Do not delete, move, or rename until user confirms.
Sync doc/rules.md
- If repo has
```
doc/rules.md
```
  or
```
docs/rules.md
```
  : update the "Context-Specific Rules" (or equivalent) list to match current
```
.mdc
```
  files and their globs/scope. Keep doc and rules directory in sync.

Output

Report: table of files (path, prefix OK?, frontmatter OK?, lines, notes); list of proposals (RENAME/MERGE/DELETE with reason and target).
Closing line: "Do zastosowania: potwierdź zmiany lub wywołaj agenta rules-keeper."
No destructive changes without explicit user confirmation.

Reference

For full prefix table and conventions, see reference.md.