review-rule

Reviews Claude Code rule files for convention compliance and validates path globs against the repository.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/sagittaras/agentic-workflow --skill review-rule-sagittaras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-rule
Source: https://github.com/sagittaras/agentic-workflow/tree/main/skills/review-rule
Command: npx skills add https://github.com/sagittaras/agentic-workflow --skill review-rule-sagittaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A broken rule file never crashes — a wrong glob silently means the rules never load into context, and nobody notices. This Skill provides an independent, clean-context review of Claude Code rule files so defects are caught before the rules ship. ## Core Features & Use Cases - Convention Compliance Check: Verifies file naming, frontmatter fields, template structure, and language against the write-rule conventions. - Glob Verification: Tests every paths pattern with the Glob tool against the real repository structure, flagging patterns that match nothing or match too broadly. - Conflict Detection: Checks the rule against CLAUDE.md and sibling rules for contradictions or duplications, with special handling for user-level rules. - Use Case: After writing or editing a rule in .claude/rules/, run this review to get a verdict (Approved / Returned for rework) with findings ranked by severity — blocking issues, recommendations, and notes — before the rule goes live. ## Quick Start Ask the assistant to review the rule file at .claude/rules/testing.md against the plugin conventions and verify its globs match real files in this repository.

Frequently Asked Questions about review-rule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a Claude Code rule file before publishing it?

Invoke the review-rule skill with the path to the rule, the plugin root, and the repository root. It checks naming, frontmatter, template structure, enforceability of each rule, and returns a verdict with findings ranked by severity.

How to validate that paths globs in a rule actually match files?

The skill runs every pattern from the rule's paths field through the Glob tool against the repository root. A pattern matching zero files is a blocking finding, since such a rule would never load into context.

Does the review-rule skill fix the issues it finds?

No, it never edits the reviewed files. It only reports findings with concrete fix recommendations, keeping the reviewer independent from the author so the approval process stays unbiased.

What happens when a rule conflicts with CLAUDE.md or other rules?

A contradiction with CLAUDE.md or sibling rules is a blocking finding, because the model would unpredictably follow one of the conflicting instructions. For user-level rules, only conflicts within ~/.claude/rules are blocking.

When should I use review-rule instead of write-rule?

Use review-rule only to assess a finished or edited rule; use write-rule to author or repair one. The write-rule skill typically invokes review-rule automatically as a subagent after each revision round.