skills.rest
Unsupervisedcom
UnsupervisedcomOFFICIAL
Explore all skills by this author →
WebsiteGitHub

deepwork_rules

Create Markdown file-change rules under .deepwork/rules/ for AI session governance.

49|3|Updated Jan 11, 2026
Search Tags:#automation#markdown#code-review#documentation-sync#policy-enforcement#AI-workflow#rule-definition
One-click install
npx skills add https://github.com/Unsupervisedcom/deepwork --skill deepwork-rules-unsupervisedcom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deepwork_rules
Source: https://github.com/Unsupervisedcom/deepwork/tree/main/.claude/skills/deepwork_rules
Command: npx skills add https://github.com/Unsupervisedcom/deepwork --skill deepwork-rules-unsupervisedcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured mechanism to create and maintain file-change rules that enforce team guidelines during AI-driven sessions, helping teams prevent drift in documentation and code reviews.

Core Features & Use Cases

  • Define Markdown rule files under .deepwork/rules/ with metadata fields such as detection mode, patterns, and actions.
  • Rules are evaluated at the Stop hook, ensuring changes are checked after a complete agent turn.
  • Use cases include ensuring documentation stays in sync with code changes, enforcing architectural guidelines, and triggering appropriate governance prompts or commands.

Quick Start

Use the Skill tool to define a new rule with the /deepwork_rules.define command and specify which files to monitor and what action to take when changes occur.

Frequently Asked Questions about deepwork_rules

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

FAQPage Schema
How do I enforce code review guidelines during an AI session?▼

You can enforce code review guidelines during an AI session by defining file-change rules as Markdown files. These rules are evaluated at the Stop hook to ensure changes follow team standards after a complete agent turn.

What is the best way to keep documentation in sync with code changes?▼

Keeping documentation in sync with code changes is handled by creating detection rules that trigger governance prompts or commands. This ensures documentation updates are enforced automatically when monitored files are modified.

Can I trigger custom actions when specific file patterns change?▼

Yes, you can trigger custom actions when specific file patterns change by defining detection modes and actions within your Markdown rule files. This allows you to execute governance commands or prompts based on the detected changes.

When do file-change rules execute during an AI workflow?▼

File-change rules execute at the Stop hook during an AI workflow. This ensures that all changes are checked and validated against team guidelines only after a complete agent turn finishes.

Related Skills

Explore More Software Engineering Skills→
ncrmroncrmro

deepwork_rules.define

Generate .deepwork/rules/*.md files with YAML frontmatter for file-change triggers.

Community
Advanced
EONMUNEONMUN
1

deepwork_rules

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

Official
Basic
ncrmroncrmro

deepwork_rules

Create and enforce file-change rules stored as Markdown frontmatter in .deepwork/rules/.

Community
Intermediate
ricablericable

Writing Hookify Rules

Create Hookify rule files with YAML frontmatter and Markdown message bodies.

Community
Intermediate