implement-rule

Generate checks, OpenGrep patterns, and fixtures for existing rule skeletons.

11|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/reporails/rules --skill implement-rule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-rule
Source: https://github.com/reporails/rules/tree/main/.claude/skills/implement-rule
Command: npx skills add https://github.com/reporails/rules --skill implement-rule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of checks, OpenGrep patterns, and fixtures for an existing rule skeleton.

Core Features & Use Cases

  • Generate frontmatter-backed checks for existing rules
  • Create deterministic OpenGrep patterns and semantic checks
  • Produce realistic pass/fail fixtures to validate rules
  • Coordinate rule resolution across core and agent-specific rules

Quick Start

Run /implement-rule <coordinate> [--agent <name>] [--dry-run] to scaffold rule checks, patterns, and fixtures for the specified rule.

Frequently Asked Questions about implement-rule

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

FAQPage Schema
How do I generate OpenGrep patterns and test fixtures for an existing rule skeleton?

Rule-implementation automation works by extracting frontmatter metadata from an existing rule skeleton, then generating deterministic OpenGrep patterns, semantic checks, and realistic pass/fail fixtures to validate the rule.

How do I automate test coverage for frontmatter-backed rule checks?

Automate test coverage by running the implementation command with a rule coordinate and optional agent flag, which scaffolds semantic checks and produces realistic pass/fail fixtures to validate the rule.

Can I generate checks for agent-specific rules without immediately applying them?

Yes, you can generate checks for agent-specific rules without applying them by using the dry-run flag with the implementation command, previewing the generated OpenGrep patterns and fixtures before committing.

Do I need an existing rule skeleton before scaffolding checks and fixtures?

Yes, you need an existing rule skeleton with frontmatter metadata, because the implementation process extracts this metadata to drive deterministic OpenGrep pattern generation and realistic fixture creation.

What is the best way to coordinate rule implementation across core and agent-specific rules?

The best way to coordinate rule implementation is using a coordinate-driven workflow that applies frontmatter-driven metadata extraction to generate checks and fixtures for both core and agent-specific rules.