deepwork_rules.define

Create DeepWork rule files with YAML frontmatter and trigger patterns.

1|Updated Jun 30, 2025
One-click install
npx skills add https://github.com/EONMUN/EONMUN --skill deepwork-rules-define
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deepwork_rules.define
Source: https://github.com/EONMUN/EONMUN/tree/main/.claude/skills/deepwork_rules.define
Command: npx skills add https://github.com/EONMUN/EONMUN --skill deepwork-rules-define

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a structured DeepWork rule that triggers when specified files change, enabling teams to enforce guidelines around documentation sync, code reviews, and automated commands.

Core Features & Use Cases

  • Defines trigger patterns and optional safety/set/pair configurations to control when rules fire.
  • Guides users through crafting deterministic rules that keep projects in sync and compliant.
  • Use Case: When config files change, automatically prompt to review related documentation or trigger a code-review checklist.

Quick Start

Define a new rule by creating a file in .deepwork/rules/ with a YAML frontmatter and a Markdown body that describes the trigger files and expected actions.

Frequently Asked Questions about deepwork_rules.define

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

FAQPage Schema
How do I automate code review requirements when specific files change?

You can automate code review requirements by defining a rule file with YAML frontmatter that specifies trigger patterns for file changes and an actionable instruction body to enforce guidelines when those files are modified.

What's the best way to keep documentation in sync with config file changes?

Keeping documentation in sync with config file changes is achieved by creating a DeepWork rule that triggers on config file modifications, automatically prompting users to review related documentation or trigger a checklist.

How do I define file-change rules for process automation across teams?

To define file-change rules for process automation, create a file in the .deepwork/rules/ directory with YAML frontmatter containing trigger patterns and a Markdown body describing the expected actions.

Can I configure safety or pair settings for file change triggers?

Yes, you can optionally configure safety, set, and pair configurations alongside trigger patterns in the YAML frontmatter to control when and how file-change rules fire for your project.

Do I need YAML frontmatter to set up automated file change rules?

Yes, YAML frontmatter is required in the rule file to define trigger patterns for file changes, while the Markdown body contains the actionable instruction that executes when the rule fires.

When should I use file-change rules for automated governance?

Use file-change rules for automated governance when you need to enforce documentation sync, code review requirements, or process automation across teams as specified files are modified.