MCPInstall

enforce-rules-format

by zernie

Validate that all rules have proper enforcement classification (enforce/check/guidance)

Installs
433
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/zernie/vigiles --skill enforce-rules-format
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads enforce-rules-format automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Validate that every rule in the project's instruction files has a proper enforcement classification, and fix any that are missing.

Instructions

Step 1: Detect Format

Check which format the project uses:

v2 (spec-based): Look for CLAUDE.md.spec.ts or any *.spec.ts files. If found, this is a v2 project — rules must use enforce(), check(), or guidance().

v1 (hand-written): Look for CLAUDE.md, AGENTS.md, .cursorrules. If found without a spec file, this is a v1 project — rules need **Enforced by:** or **Guidance only** annotations.

Step 2: Validate

For v2 specs:

The TypeScript type system already prevents unannotated rules — you can't create a rule without calling enforce(), check(), or guidance(). So focus on:

  1. Do enforce() rules reference real linter rules? Run npx vigiles compile to check.
  2. Are there guidance rules that COULD be enforce()? Check linter configs for matching rules.
  3. Are there check() assertions that could be delegated to a linter? Suggest enforce() instead.
npx vigiles compile
npx vigiles discover

For v1 hand-written files:

Scan for ### headings. Each must have one of:

  • **Enforced by:** \linter/rule-name``
  • **Guidance only** — reason
  • <!-- vigiles-disable -->

Report missing annotations with a summary table.

Step 3: Fix Issues

For each issue found:

  1. Check the project's linter configuration for matching rules
  2. Suggest enforce("linter/rule") (v2) or **Enforced by:** \linter/rule`` (v1)
  3. If no linter rule exists, suggest guidance() (v2) or **Guidance only** (v1)
  4. Ask the user before making changes

Step 4: Suggest Migration

If the project uses v1 format, suggest migrating to v2 specs for type safety:

Your rules could benefit from type-safe specs. Run the adopt-spec skill to convert your CLAUDE.md to a typed .spec.ts file.

Step 5: Verify

Run the appropriate command:

# v2
npx vigiles compile && npx vigiles check

# validate
npx vigiles check

Report the validation result.

FAQ

What does the enforce-rules-format skill do?

Validate that all rules have proper enforcement classification (enforce/check/guidance)

How do I install enforce-rules-format?

Run npx skills add https://github.com/zernie/vigiles --skill enforce-rules-format in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/enforce-rules-format/ (personal) or .claude/skills/enforce-rules-format/ (project).

Which AI agents can use enforce-rules-format?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is enforce-rules-format safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains enforce-rules-format?

It is published by zernie in zernie/vigiles. It has 433 recorded installs.

More from zernie/vigiles

View all →

edit-spec

zernie/vigiles

Edit a vigiles .spec.ts to change a compiled instruction file (CLAUDE.md / AGENTS.md) — add, modify, or remove a rule, section, command, or file pointer (including a request to add a "key file" — the keyFiles field is deprecated). Use whenever you need to change a CLAUDE.md/AGENTS.md that carries a vigiles hash (edit the spec, never the artifact), including adding a new enforce()/check()/guidance() rule.

Code Quality & Workflow2.1K installs

strengthen

zernie/vigiles

Upgrade a vigiles spec's guidance() rules to enforce() — scan the guidance rules in a CLAUDE.md/AGENTS.md spec and find existing linter rules (ESLint, Ruff, Clippy, Pylint, RuboCop, Stylelint) that back them. Use when asked to strengthen, harden, or make vigiles rules enforceable; NOT for general linting or fixing lint errors.

Code Quality & Workflow2.1K installs

test-harness

zernie/vigiles

Install vigiles and test a Claude Code harness — hooks, skills, agents, settings, CLAUDE.md — by picking the right tier (unit / deterministic / eval) and writing a test that passes. Use to check that a hook fires or blocks, that a skill triggers, that injected context lands; or to observe a run — which tools it called, whether it stayed inside its declared allowed-tools, what files and side effects it produced, how to intercept a call without executing it.

Testing & QA2.1K installs

linter-docs

zernie/vigiles

Deep linter reference for authoring or debugging a vigiles enforce() rule — plugin tables, AST selectors, type-aware rules, auto-fix, and edge cases for ESLint, Ruff, Pylint, RuboCop, Stylelint, and Clippy. Use when you need the exact rule name or config for a specific linter, not for running a linter. (JVM/Go linters — detekt, ktlint, Checkstyle, golangci-lint — and Cedar have no deep-dive file yet; their reference lives in docs/linter-support.md.)

Docs & Writing2K installs

adopt-spec

zernie/vigiles

Adopt a typed .spec.ts for an existing hand-written CLAUDE.md — start from the file you already have, non-destructively

Code Quality & Workflow1.8K installs

debug-my-harness

zernie/vigiles

Diagnose why an agent harness misbehaved by reading the local flight-recorder ledger (.vigiles/runs.jsonl) — which skills fired or got hijacked, which hooks blocked or wrongly allowed, which subagent tool-contract violations happened, and how a skill's trigger rate moved. Use when asked why a skill stopped firing, why a hook didn't block, why the wrong skill ran, or to debug/investigate what the harness actually did. NOT for writing new rules (use strengthen) or editing the spec (use edit-spec).

Code Quality & Workflow1.5K installs

Popular other skills

View category →

hyperframes-cli

heygen-com/hyperframes

The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.

1.3M installs

triage

mattpocock/skills

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

1M installs

ask-matt

mattpocock/skills

Ask which skill or flow fits your situation. A router over the skills in this repo.

778.4K installs

to-questionnaire

mattpocock/skills

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

508.9K installs

wait-what

mattpocock/skills

Stop. That last message did not land: re-pitch it.

459.7K installs

loop-me

mattpocock/skills

Grill me about specs for the workflows I want to build, within this workspace.

447.9K installs