wfc-rules

Enforce Markdown-defined coding rules via PreToolUse hooks.

Updated Aug 23, 2026

Search Tags:#code quality #coding standards #developer productivity #enforcement #pre-commit hooks #rule engine

Ready to run

npx skills add https://github.com/sam-fakhreddine/wfc --skill wfc-rules

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wfc-rules
Source: https://github.com/sam-fakhreddine/wfc/tree/main/wfc/skills/wfc-rules
Command: npx skills add https://github.com/sam-fakhreddine/wfc --skill wfc-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows you to define and automatically enforce project-specific coding standards and conventions without writing any code, ensuring consistency and adherence to team guidelines.

Core Features & Use Cases

Markdown-based Rules: Define rules using simple Markdown files with YAML frontmatter.
PreToolUse Hooks: Rules are automatically triggered before tool usage, preventing violations.
Customizable Actions: Choose to block or warn on rule violations.
Use Case: Automatically prevent developers from committing .env files or ensure all TODO comments include a ticket reference.

Quick Start

Create a rule file in the .wfc/rules/ directory to define a new coding standard.

Frequently Asked Questions about wfc-rules

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

FAQPage Schema

How do I enforce coding standards automatically before commits?▼

Markdown-based coding standards are defined using simple Markdown files with YAML frontmatter, configured in a specific project directory to establish rule conditions and actions without writing code.

Can I prevent committing .env files using pre-commit hooks?▼

Yes, you can prevent committing .env files by configuring a rule to block violations, which triggers automatically through PreToolUse hooks that evaluate file paths and content against your defined conditions.

How do I ensure TODO comments include a ticket reference in my workflow?▼

You can require TODO comments to include a ticket reference by defining a rule that evaluates file content and blocks or warns developers when the condition is not met during the development workflow.

Do I need to write custom code to set up project-specific coding conventions?▼

No, you do not need to write custom code to set up project-specific coding conventions; rules are defined entirely using simple Markdown files with YAML frontmatter to establish your team's best practices.

What can I configure pre-commit hooks to evaluate besides file content?▼

Pre-commit hooks can evaluate file paths and bash commands in addition to file content, checking these elements against defined conditions to enforce team conventions and project-specific rules.