rule-review

Audit agent-rules files across seven dimensions and emit line-referenced findings.

3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/bpawlakj/ai-devkit --skill rule-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule-review
Source: https://github.com/bpawlakj/ai-devkit/tree/main/claude/skills/rule-review
Command: npx skills add https://github.com/bpawlakj/ai-devkit --skill rule-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you verify that an agent-rules file is correct, efficient, non-redundant, and actually reachable—so your agent follows the rules instead of ignoring or contradicting them.

Core Features & Use Cases

  • Evidence-based auditing across seven dimensions: checks length, embedded code/config blocks, language precision, redundancy with your auto-active rules layer, ordering, cross-tool drift, and dead rules using grep.
  • Cross-tool drift detection: compares common sibling rule sources (e.g., AGENTS.md vs CLAUDE.md vs GitHub Copilot vs Cursor) to find contradictions for the same scope.
  • Safe remediation with --fix: applies only non-destructive, safe rewrites (e.g., removing redundancy, reordering critical sections) and flags anything that requires manual attention.

Quick Start

Run a read-only audit of your rules file by instructing the AI:
“Review AGENTS.md for redundancy, drift, ordering, and dead rules.”

Frequently Asked Questions about rule-review

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

FAQPage Schema
How do I audit an AGENTS.md file for redundancy and dead rules?

Cross-tool drift detection compares common sibling rule sources like AGENTS.md, CLAUDE.md, GitHub Copilot, and Cursor configurations to find contradictions for the same scope, ensuring your agent consistently follows intended constraints.

What is cross-tool drift in agent-rules files and how do I detect it?

Cross-tool drift occurs when sibling rule sources like AGENTS.md and CLAUDE.md contain contradictions for the same scope. Detection compares these common files to find inconsistencies and emits a structured report with line-referenced findings.

Can I automatically fix agent-rules files without breaking existing constraints?

Auditing agent-rules files checks seven dimensions: length, embedded code blocks, language precision, redundancy, ordering, cross-tool drift, and dead-rule reachability. This evidence-based approach ensures your agent follows constraints instead of ignoring them.

How do I check if rules in CLAUDE.md are unreachable or dead?

Agent-rules files are audited across seven dimensions: length, embedded code blocks, language precision, redundancy, ordering, cross-tool drift, and dead-rule reachability. Evidence-backed verdicts ensure agents follow intended constraints consistently.

Does agent-rules auditing work with both AGENTS.md and Cursor configurations?

Agent-rules auditing applies when authoring or maintaining AGENTS.md, CLAUDE.md, and related rule documents. Cross-tool drift detection compares common sibling rule sources including GitHub Copilot and Cursor to find scope contradictions.

What dimensions should a policy audit cover for prompt engineering rules?

A policy audit for prompt engineering rules covers seven dimensions: length, embedded code blocks, language precision, redundancy, ordering, cross-tool drift, and dead-rule reachability. Each dimension produces evidence-backed findings with line references.