deepwork_rules

Enforce file-change rules from markdown with YAML frontmatter at the Stop hook.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates enforcement of file-change rules during AI agent sessions to ensure compliance with team guidelines, documentation updates, and code-review triggers.

Core Features & Use Cases

  • Rule creation and management: Define markdown-based rules under .deepwork/rules/ with YAML frontmatter to govern actions and detections.
  • Stop-hook execution: Rules are evaluated at the Stop hook, batching changes and applying governance at the end of an agent's turn.
  • Use Case: Enforce documentation sync when configuration files change or require security reviews when authentication code is modified.

Quick Start

Use the deepwork_rules skill to define a new rule that prompts for code-review when a matched file changes.

Frequently Asked Questions about deepwork_rules

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

FAQPage Schema
How do I enforce file-change rules during AI agent sessions?

You can enforce file-change rules by defining markdown-based rules with YAML frontmatter under the .deepwork/rules/ directory, which are automatically evaluated and applied at the Stop hook when an AI agent finishes its turn.

What is the best way to automate policy enforcement for documentation sync?

Automating policy enforcement for documentation sync is handled by configuring file pattern detection rules that trigger governance actions, ensuring required documentation updates are flagged whenever matching configuration files are modified.

Can I trigger code reviews automatically when authentication code is modified?

Yes, you can trigger code reviews automatically by creating a rule that specifies authentication code file patterns, which then prompts a review action when those files are changed during an AI workflow.

How do architectural decision tracking rules work with collaborative AI workflows?

Architectural decision tracking rules work by batching file changes at the Stop hook, applying governance evaluations at the end of an agent's turn to maintain compliance within collaborative AI workflows.

Do I need specific dependencies to run deepwork_rules for governance automation?

No specific dependencies are required to run governance automation, as the rules are stored as standard markdown files with YAML frontmatter and executed natively at the configured Stop hook.

Why are my file-change rules not triggering at the end of an AI session?

File-change rules may not trigger if the detection modes or file patterns in the YAML frontmatter are misconfigured, or if the session does not properly reach the Stop hook where governance actions are batched and executed.