codify-rule

Converts review findings into operator-approved Handbook rule files under omnigrid/handbooks.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/MohamedSayedK/omnigrid --skill codify-rule-mohamedsayedk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codify-rule
Source: https://github.com/MohamedSayedK/omnigrid/tree/main/assets/core/skills/codify-rule
Command: npx skills add https://github.com/MohamedSayedK/omnigrid --skill codify-rule-mohamedsayedk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a code review catches a mistake, that lesson is usually lost after the PR merges. This Skill turns a one-off review comment into a standing, committed Handbook rule so the same mistake is flagged on every future PR. ## Core Features & Use Cases - Guided rule capture: Walks the operator from a raw review finding through bucket selection (domain, architecture, general, language), slug derivation, and a five-section rule template. - Mandatory approval gate: Previews the complete file and writes nothing until the operator explicitly confirms, keeping the Handbook operator-curated rather than auto-generated. - Advisory-by-default enforcement: Writes rules as advisory, with an opt-in --blocking flag reserved for security or data-loss concerns. - Use Case: A reviewer catches a missing Stripe webhook signature check. Run the skill with the review comment, pick the domain bucket, and it writes omnigrid/handbooks/domain/stripe-webhooks/verify-webhook-signatures.md ready to commit. ## Quick Start Run /codify-rule followed by a one-sentence description of the review finding you want to turn into a standing Handbook rule.

Frequently Asked Questions about codify-rule

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

FAQPage Schema
How do I turn a code review comment into a permanent rule?▼

Run /codify-rule with the review comment or a one-sentence description of the mistake. The skill guides you through picking a handbook bucket, drafting the rule sections, and previewing the file before anything is written to omnigrid/handbooks/.

What handbook buckets are available for coding rules?▼

Four buckets exist: domain (knowledge tied to a problem area, loaded via paths frontmatter), architecture (layering and design patterns), general (cross-cutting conventions), and language (rules for a specific language like TypeScript or Go).

Does codify-rule write files automatically without approval?▼

No. The skill is operator-curated: it shows the complete draft with the resolved path and waits for an explicit yes before writing. Choosing edit re-shows the draft, and no aborts with nothing written.

When should I use the --blocking flag on a handbook rule?▼

Use --blocking only for security, data-loss, or hard contractual requirements. Rules default to advisory because a blocking rule introduced too early creates friction and tends to get disabled.

What happens if the handbook rule file already exists?▼

The skill offers three options: append the new entry with a separator (recommended for a different miss in the same area), overwrite the existing file, or cancel. For domain handbooks, append merges and dedupes the paths globs.