Add deepwork rule for uv.lock updates (#84)

* Add uv-lock-sync rule to auto-update uv.lock

Automatically runs `uv sync` when pyproject.toml is modified to keep
the lock file in sync with dependency changes.

* Clarify that rules fire at Stop hook in job.yml description

Updated deepwork_rules job.yml description to make clear that:
- Rules evaluate at the Stop hook when agents finish their turn
- This includes when sub-agents complete their work
- Command actions run at this time, prompt actions block
- Added uv sync example use case for command actions

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: nhorton

.claude/skills/deepwork_rules.define/SKILL.md

@@ -272,17 +272,25 @@ Manages rules that automatically trigger when certain files change during an AI
 Rules help ensure that code changes follow team guidelines, documentation is updated,
 and architectural decisions are respected.
 
+IMPORTANT: Rules are evaluated at the "Stop" hook, which fires when an agent finishes its turn.
+This includes when sub-agents complete their work. Rules are NOT evaluated immediately after
+each file edit - they batch up and run once at the end of the agent's response cycle.
+- Command action rules: Execute their command (e.g., `uv sync`) when the agent stops
+- Prompt action rules: Display instructions to the agent, blocking until addressed
+
 Rules are stored as individual markdown files with YAML frontmatter in the `.deepwork/rules/`
 directory. Each rule file specifies:
 - Detection mode: trigger/safety, set (bidirectional), or pair (directional)
 - Patterns: Glob patterns for matching files, with optional variable capture
+- Action type: prompt (default) to show instructions, or command to run a shell command
 - Instructions: Markdown content describing what the agent should do
 
 Example use cases:
 - Update installation docs when configuration files change
 - Require security review when authentication code is modified
 - Ensure API documentation stays in sync with API code
 - Enforce source/test file pairing
+- Auto-run `uv sync` when pyproject.toml changes (command action)
 
 
 ## Required Inputs

.claude/skills/deepwork_rules/SKILL.md

@@ -13,17 +13,25 @@ Manages rules that automatically trigger when certain files change during an AI
 Rules help ensure that code changes follow team guidelines, documentation is updated,
 and architectural decisions are respected.
 
+IMPORTANT: Rules are evaluated at the "Stop" hook, which fires when an agent finishes its turn.
+This includes when sub-agents complete their work. Rules are NOT evaluated immediately after
+each file edit - they batch up and run once at the end of the agent's response cycle.
+- Command action rules: Execute their command (e.g., `uv sync`) when the agent stops
+- Prompt action rules: Display instructions to the agent, blocking until addressed
+
 Rules are stored as individual markdown files with YAML frontmatter in the `.deepwork/rules/`
 directory. Each rule file specifies:
 - Detection mode: trigger/safety, set (bidirectional), or pair (directional)
 - Patterns: Glob patterns for matching files, with optional variable capture
+- Action type: prompt (default) to show instructions, or command to run a shell command
 - Instructions: Markdown content describing what the agent should do
 
 Example use cases:
 - Update installation docs when configuration files change
 - Require security review when authentication code is modified
 - Ensure API documentation stays in sync with API code
 - Enforce source/test file pairing
+- Auto-run `uv sync` when pyproject.toml changes (command action)
 
 
 ## Available Steps

.deepwork/jobs/deepwork_rules/job.yml

@@ -6,17 +6,25 @@ description: |
   Rules help ensure that code changes follow team guidelines, documentation is updated,
   and architectural decisions are respected.
 
+  IMPORTANT: Rules are evaluated at the "Stop" hook, which fires when an agent finishes its turn.
+  This includes when sub-agents complete their work. Rules are NOT evaluated immediately after
+  each file edit - they batch up and run once at the end of the agent's response cycle.
+  - Command action rules: Execute their command (e.g., `uv sync`) when the agent stops
+  - Prompt action rules: Display instructions to the agent, blocking until addressed
+
   Rules are stored as individual markdown files with YAML frontmatter in the `.deepwork/rules/`
   directory. Each rule file specifies:
   - Detection mode: trigger/safety, set (bidirectional), or pair (directional)
   - Patterns: Glob patterns for matching files, with optional variable capture
+  - Action type: prompt (default) to show instructions, or command to run a shell command
   - Instructions: Markdown content describing what the agent should do
 
   Example use cases:
   - Update installation docs when configuration files change
   - Require security review when authentication code is modified
   - Ensure API documentation stays in sync with API code
   - Enforce source/test file pairing
+  - Auto-run `uv sync` when pyproject.toml changes (command action)
 
 changelog:
   - version: "0.1.0"

.deepwork/rules/uv-lock-sync.md

@@ -0,0 +1,15 @@
+---
+name: UV Lock Sync
+trigger: pyproject.toml
+action:
+  command: uv sync
+compare_to: prompt
+---
+
+# UV Lock Sync
+
+Automatically runs `uv sync` when `pyproject.toml` is modified to keep
+`uv.lock` in sync with dependency changes.
+
+This ensures the lock file is always up-to-date when dependencies are
+added, removed, or updated in pyproject.toml.

.gemini/skills/deepwork_rules/define.toml

@@ -275,17 +275,25 @@ Manages rules that automatically trigger when certain files change during an AI
 Rules help ensure that code changes follow team guidelines, documentation is updated,
 and architectural decisions are respected.
 
+IMPORTANT: Rules are evaluated at the "Stop" hook, which fires when an agent finishes its turn.
+This includes when sub-agents complete their work. Rules are NOT evaluated immediately after
+each file edit - they batch up and run once at the end of the agent's response cycle.
+- Command action rules: Execute their command (e.g., `uv sync`) when the agent stops
+- Prompt action rules: Display instructions to the agent, blocking until addressed
+
 Rules are stored as individual markdown files with YAML frontmatter in the `.deepwork/rules/`
 directory. Each rule file specifies:
 - Detection mode: trigger/safety, set (bidirectional), or pair (directional)
 - Patterns: Glob patterns for matching files, with optional variable capture
+- Action type: prompt (default) to show instructions, or command to run a shell command
 - Instructions: Markdown content describing what the agent should do
 
 Example use cases:
 - Update installation docs when configuration files change
 - Require security review when authentication code is modified
 - Ensure API documentation stays in sync with API code
 - Enforce source/test file pairing
+- Auto-run `uv sync` when pyproject.toml changes (command action)
 
 
 ## Required Inputs

.gemini/skills/deepwork_rules/index.toml

@@ -17,17 +17,25 @@ Manages rules that automatically trigger when certain files change during an AI
 Rules help ensure that code changes follow team guidelines, documentation is updated,
 and architectural decisions are respected.
 
+IMPORTANT: Rules are evaluated at the "Stop" hook, which fires when an agent finishes its turn.
+This includes when sub-agents complete their work. Rules are NOT evaluated immediately after
+each file edit - they batch up and run once at the end of the agent's response cycle.
+- Command action rules: Execute their command (e.g., `uv sync`) when the agent stops
+- Prompt action rules: Display instructions to the agent, blocking until addressed
+
 Rules are stored as individual markdown files with YAML frontmatter in the `.deepwork/rules/`
 directory. Each rule file specifies:
 - Detection mode: trigger/safety, set (bidirectional), or pair (directional)
 - Patterns: Glob patterns for matching files, with optional variable capture
+- Action type: prompt (default) to show instructions, or command to run a shell command
 - Instructions: Markdown content describing what the agent should do
 
 Example use cases:
 - Update installation docs when configuration files change
 - Require security review when authentication code is modified
 - Ensure API documentation stays in sync with API code
 - Enforce source/test file pairing
+- Auto-run `uv sync` when pyproject.toml changes (command action)
 
 
 ## Available Steps

src/deepwork/standard_jobs/deepwork_rules/job.yml

@@ -6,17 +6,25 @@ description: |
   Rules help ensure that code changes follow team guidelines, documentation is updated,
   and architectural decisions are respected.
 
+  IMPORTANT: Rules are evaluated at the "Stop" hook, which fires when an agent finishes its turn.
+  This includes when sub-agents complete their work. Rules are NOT evaluated immediately after
+  each file edit - they batch up and run once at the end of the agent's response cycle.
+  - Command action rules: Execute their command (e.g., `uv sync`) when the agent stops
+  - Prompt action rules: Display instructions to the agent, blocking until addressed
+
   Rules are stored as individual markdown files with YAML frontmatter in the `.deepwork/rules/`
   directory. Each rule file specifies:
   - Detection mode: trigger/safety, set (bidirectional), or pair (directional)
   - Patterns: Glob patterns for matching files, with optional variable capture
+  - Action type: prompt (default) to show instructions, or command to run a shell command
   - Instructions: Markdown content describing what the agent should do
 
   Example use cases:
   - Update installation docs when configuration files change
   - Require security review when authentication code is modified
   - Ensure API documentation stays in sync with API code
   - Enforce source/test file pairing
+  - Auto-run `uv sync` when pyproject.toml changes (command action)
 
 changelog:
   - version: "0.1.0"