deepwork 0.3.0__tar.gz → 0.3.1__tar.gz

{deepwork-0.3.0 → deepwork-0.3.1}/.claude/skills/commit/SKILL.md

@@ -25,7 +25,7 @@ Steps:
 
 1. **test** - Pull latest code and run the test suite until all tests pass
 2. **lint** - Format and lint code with ruff using a sub-agent (requires: test)
-3. **commit_and_push** - Review changed files, commit, and push to remote (requires: lint)
+3. **commit_and_push** - Verify changed files, commit, and push to remote (requires: lint)
 
 ## Execution Instructions
 

{deepwork-0.3.0 → deepwork-0.3.1}/.claude/skills/commit.commit_and_push/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: commit.commit_and_push
-description: "Review changed files, commit, and push to remote"
+description: "Verify changed files, commit, and push to remote"
 user-invocable: false
 hooks:
   Stop:
@@ -8,8 +8,8 @@ hooks:
         - type: prompt
           prompt: |
             Verify the commit is ready:
-            1. Changed files list was reviewed with user
-            2. User confirmed the files match expectations
+            1. Changed files list was reviewed by the agent
+            2. Files match what was modified during this session (or unexpected changes were investigated)
             3. Commit was created with appropriate message
             4. Changes were pushed to remote
             If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
@@ -29,17 +29,17 @@ Before proceeding, confirm these steps are complete:
 
 ## Instructions
 
-**Goal**: Review changed files, commit, and push to remote
+**Goal**: Verify changed files, commit, and push to remote
 
 # Commit and Push
 
 ## Objective
 
-Review the changed files with the user, create a commit with an appropriate message, and push to the remote repository.
+Review the changed files to verify they match the agent's expectations, create a commit with an appropriate message, and push to the remote repository.
 
 ## Task
 
-Present the list of changed files for user review, ensure they match expectations, then commit and push the changes.
+Check the list of changed files against what was modified during this session, ensure they match expectations, then commit and push the changes.
 
 ### Process
 
@@ -49,31 +49,26 @@ Present the list of changed files for user review, ensure they match expectation
    ```
    Also run `git diff --stat` to see a summary of changes.
 
-2. **Present changes to the user for review**
+2. **Verify changes match expectations**
 
-   Use the AskUserQuestion tool to ask structured questions about the changes:
+   Compare the changed files against what you modified during this session:
+   - Do the modified files match what you edited?
+   - Are there any unexpected new files?
+   - Are there any unexpected deleted files?
+   - Do the line counts seem reasonable for the changes you made?
 
-   Show the user:
-   - List of modified files
-   - List of new files
-   - List of deleted files
-   - Summary of changes (lines added/removed)
+   If changes match expectations, proceed to commit.
 
-   Ask them to confirm:
-   - "Do these changed files match your expectations?"
-   - Provide options: "Yes, proceed with commit" / "No, let me review first" / "No, some files shouldn't be included"
+   If there are unexpected changes:
+   - Investigate why (e.g., lint auto-fixes, generated files)
+   - If they're legitimate side effects of your work, include them
+   - If they're unrelated or shouldn't be committed, use `git restore` to discard them
 
-3. **Handle user response**
-
-   - If user confirms, proceed to commit
-   - If user wants to review first, wait for them to come back
-   - If user says some files shouldn't be included, ask which files to exclude and use `git restore` or `git checkout` to unstage them
-
-4. **Stage all appropriate changes**
+3. **Stage all appropriate changes**
    ```bash
    git add -A
    ```
-   Or stage specific files if user excluded some.
+   Or stage specific files if some were excluded.
 
 5. **View recent commit messages for style reference**
    ```bash
@@ -102,8 +97,8 @@ Present the list of changed files for user review, ensure they match expectation
 
 ## Quality Criteria
 
-- Changed files list was presented to user
-- User explicitly confirmed the files match expectations
+- Changed files list was reviewed by the agent
+- Files match what was modified during this session (or unexpected changes were investigated and handled)
 - Commit message follows project conventions
 - Commit was created successfully
 - Changes were pushed to remote
@@ -111,7 +106,7 @@ Present the list of changed files for user review, ensure they match expectation
 
 ## Context
 
-This is the final step of the commit workflow. It ensures the user has reviewed and approved the changes before they are committed and pushed. This prevents accidental commits of unintended files or changes.
+This is the final step of the commit workflow. The agent verifies that the changed files match its own expectations from the work done during the session, then commits and pushes. This catches unexpected changes while avoiding unnecessary user interruptions.
 
 
 ### Job Context

{deepwork-0.3.0 → deepwork-0.3.1}/.claude/skills/deepwork_rules/SKILL.md

@@ -13,10 +13,17 @@ 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:
@@ -24,6 +31,7 @@ Example use cases:
 - 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-0.3.0 → deepwork-0.3.1}/.claude/skills/deepwork_rules.define/SKILL.md

@@ -272,10 +272,17 @@ 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:
@@ -283,6 +290,7 @@ Example use cases:
 - 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

{deepwork-0.3.0 → deepwork-0.3.1}/.deepwork/jobs/commit/job.yml

@@ -1,5 +1,5 @@
 name: commit
-version: "1.0.0"
+version: "1.0.1"
 summary: "Run tests, lint, and commit code changes"
 description: |
   A workflow for preparing and committing code changes with quality checks.
@@ -14,6 +14,8 @@ description: |
   3. commit_and_push - Review changes and commit/push
 
 changelog:
+  - version: "1.0.1"
+    changes: "Changed file review from user confirmation to agent self-verification - agent now checks files match its own expectations instead of asking user every time"
   - version: "1.0.0"
     changes: "Initial job creation"
 
@@ -56,7 +58,7 @@ steps:
 
   - id: commit_and_push
     name: "Commit and Push"
-    description: "Review changed files, commit, and push to remote"
+    description: "Verify changed files, commit, and push to remote"
     instructions_file: steps/commit_and_push.md
     inputs: []
     outputs: []
@@ -66,8 +68,8 @@ steps:
       after_agent:
         - prompt: |
             Verify the commit is ready:
-            1. Changed files list was reviewed with user
-            2. User confirmed the files match expectations
+            1. Changed files list was reviewed by the agent
+            2. Files match what was modified during this session (or unexpected changes were investigated)
             3. Commit was created with appropriate message
             4. Changes were pushed to remote
             If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.

deepwork-0.3.1/.deepwork/jobs/commit/steps/commit_and_push.md

@@ -0,0 +1,76 @@
+# Commit and Push
+
+## Objective
+
+Review the changed files to verify they match the agent's expectations, create a commit with an appropriate message, and push to the remote repository.
+
+## Task
+
+Check the list of changed files against what was modified during this session, ensure they match expectations, then commit and push the changes.
+
+### Process
+
+1. **Get the list of changed files**
+   ```bash
+   git status
+   ```
+   Also run `git diff --stat` to see a summary of changes.
+
+2. **Verify changes match expectations**
+
+   Compare the changed files against what you modified during this session:
+   - Do the modified files match what you edited?
+   - Are there any unexpected new files?
+   - Are there any unexpected deleted files?
+   - Do the line counts seem reasonable for the changes you made?
+
+   If changes match expectations, proceed to commit.
+
+   If there are unexpected changes:
+   - Investigate why (e.g., lint auto-fixes, generated files)
+   - If they're legitimate side effects of your work, include them
+   - If they're unrelated or shouldn't be committed, use `git restore` to discard them
+
+3. **Stage all appropriate changes**
+   ```bash
+   git add -A
+   ```
+   Or stage specific files if some were excluded.
+
+5. **View recent commit messages for style reference**
+   ```bash
+   git log --oneline -10
+   ```
+
+6. **Create the commit**
+
+   Generate an appropriate commit message based on:
+   - The changes made
+   - The style of recent commits
+   - Conventional commit format if the project uses it
+
+   ```bash
+   git commit -m "commit message here"
+   ```
+
+7. **Push to remote**
+   ```bash
+   git push
+   ```
+   If the branch has no upstream, use:
+   ```bash
+   git push -u origin HEAD
+   ```
+
+## Quality Criteria
+
+- Changed files list was reviewed by the agent
+- Files match what was modified during this session (or unexpected changes were investigated and handled)
+- Commit message follows project conventions
+- Commit was created successfully
+- Changes were pushed to remote
+- When all criteria are met, include `<promise>✓ Quality Criteria Met</promise>` in your response
+
+## Context
+
+This is the final step of the commit workflow. The agent verifies that the changed files match its own expectations from the work done during the session, then commits and pushes. This catches unexpected changes while avoiding unnecessary user interruptions.

deepwork-0.3.1/.deepwork/jobs/deepwork_rules/hooks/capture_prompt_work_tree.sh

@@ -0,0 +1,38 @@
+#!/bin/bash
+# capture_prompt_work_tree.sh - Captures the git work tree state at prompt submission
+#
+# This script creates a snapshot of ALL tracked files at the time the prompt
+# is submitted. This baseline is used for rules with compare_to: prompt and
+# created: mode to detect truly NEW files (not modifications to existing ones).
+#
+# The baseline contains ALL tracked files (not just changed files) so that
+# the rules_check hook can determine which files are genuinely new vs which
+# files existed before and were just modified.
+#
+# It also captures the HEAD commit ref so that committed changes can be detected
+# by comparing HEAD at Stop time to the captured ref.
+
+set -e
+
+# Ensure .deepwork directory exists
+mkdir -p .deepwork
+
+# Save the current HEAD commit ref for detecting committed changes
+# This is used by get_changed_files_prompt() to detect files changed since prompt,
+# even if those changes were committed during the agent response.
+git rev-parse HEAD > .deepwork/.last_head_ref 2>/dev/null || echo "" > .deepwork/.last_head_ref
+
+# Save ALL tracked files (not just changed files)
+# This is critical for created: mode rules to distinguish between:
+# - Newly created files (not in baseline) -> should trigger created: rules
+# - Modified existing files (in baseline) -> should NOT trigger created: rules
+git ls-files > .deepwork/.last_work_tree 2>/dev/null || true
+
+# Also include untracked files that exist at prompt time
+# These are files the user may have created before submitting the prompt
+git ls-files --others --exclude-standard >> .deepwork/.last_work_tree 2>/dev/null || true
+
+# Sort and deduplicate
+if [ -f .deepwork/.last_work_tree ]; then
+    sort -u .deepwork/.last_work_tree -o .deepwork/.last_work_tree
+fi

{deepwork-0.3.0/src/deepwork/standard_jobs → deepwork-0.3.1/.deepwork/jobs}/deepwork_rules/job.yml

@@ -6,10 +6,17 @@ 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:
@@ -17,6 +24,7 @@ description: |
   - 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-0.3.0/src/deepwork/standard_jobs → deepwork-0.3.1/.deepwork/jobs}/deepwork_rules/rules/skill-md-validation.md

@@ -1,6 +1,7 @@
 ---
 name: SKILL.md Validation
 trigger: "**/SKILL.md"
+compare_to: base
 ---
 A SKILL.md file has been created or modified. Please validate that it follows the required format:
 

{deepwork-0.3.0 → deepwork-0.3.1}/.deepwork/rules/architecture-documentation-accuracy.md

@@ -2,6 +2,7 @@
 name: Architecture Documentation Accuracy
 trigger: src/**/*
 safety: doc/architecture.md
+compare_to: base
 ---
 Source code in src/ has been modified. Please review doc/architecture.md for accuracy:
 1. Verify the documented architecture matches the current implementation

deepwork-0.3.1/.deepwork/rules/manual-test-created-mode.md

@@ -0,0 +1,22 @@
+---
+name: "Manual Test: Created Mode"
+created: manual_tests/test_created_mode/*.yml
+compare_to: prompt
+---
+
+# Manual Test: Created Mode (File Creation Trigger)
+
+A new test file was created in the created mode test directory!
+
+**Created:** `{created_files}`
+
+## What to do:
+
+1. Verify the created mode detection is working correctly
+2. Acknowledge with `<promise>Manual Test: Created Mode</promise>`
+
+## This tests:
+
+The "created" detection mode where rules only fire for newly created files,
+not for modifications to existing files. This is useful for enforcing standards
+on new code specifically.

deepwork-0.3.1/.deepwork/rules/new-standard-job-warning.md

@@ -0,0 +1,16 @@
+---
+name: New Standard Job Warning
+created: src/deepwork/standard_jobs/*/job.yml
+compare_to: prompt
+---
+A new standard job is being created. Standard jobs are bundled with DeepWork and will be installed in any project that uses DeepWork.
+
+**Before proceeding, verify this is intentional:**
+
+- **Standard jobs** (`src/deepwork/standard_jobs/`) - Ship with DeepWork, auto-installed in all projects that use DeepWork
+- **Repository jobs** (`.deepwork/jobs/`) - Specific to a single repository
+- **Library jobs** - Installed from external packages
+
+Unless the user **explicitly requested** creating a new standard job (not just "a job" or "a new job"), this should likely be a **repository job** in `.deepwork/jobs/` instead.
+
+If uncertain, ask the user: "Should this be a standard job (shipped with DeepWork) or a repository-specific job?"

{deepwork-0.3.0 → deepwork-0.3.1}/.deepwork/rules/readme-accuracy.md

@@ -2,6 +2,7 @@
 name: README Accuracy
 trigger: src/**/*
 safety: README.md
+compare_to: base
 ---
 Source code in src/ has been modified. Please review README.md for accuracy:
 1. Verify project overview still reflects current functionality

{deepwork-0.3.0 → deepwork-0.3.1}/.deepwork/rules/standard-jobs-source-of-truth.md

@@ -6,6 +6,7 @@ trigger:
 safety:
   - src/deepwork/standard_jobs/deepwork_jobs/**/*
   - src/deepwork/standard_jobs/deepwork_rules/**/*
+compare_to: base
 ---
 You modified files in `.deepwork/jobs/deepwork_jobs/` or `.deepwork/jobs/deepwork_rules/`.
 

deepwork-0.3.1/.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.

{deepwork-0.3.0 → deepwork-0.3.1}/.deepwork/rules/version-and-changelog-update.md

@@ -4,6 +4,7 @@ trigger: src/**/*
 safety:
   - pyproject.toml
   - CHANGELOG.md
+compare_to: base
 ---
 Source code in src/ has been modified. **You MUST evaluate whether version and changelog updates are needed.**
 

{deepwork-0.3.0 → deepwork-0.3.1}/.gemini/skills/commit/commit_and_push.toml

@@ -1,10 +1,10 @@
 # commit:commit_and_push
 #
-# Review changed files, commit, and push to remote
+# Verify changed files, commit, and push to remote
 #
 # Generated by DeepWork - do not edit manually
 
-description = "Review changed files, commit, and push to remote"
+description = "Verify changed files, commit, and push to remote"
 
 prompt = """
 # commit:commit_and_push
@@ -20,17 +20,17 @@ Before proceeding, confirm these steps are complete:
 
 ## Instructions
 
-**Goal**: Review changed files, commit, and push to remote
+**Goal**: Verify changed files, commit, and push to remote
 
 # Commit and Push
 
 ## Objective
 
-Review the changed files with the user, create a commit with an appropriate message, and push to the remote repository.
+Review the changed files to verify they match the agent's expectations, create a commit with an appropriate message, and push to the remote repository.
 
 ## Task
 
-Present the list of changed files for user review, ensure they match expectations, then commit and push the changes.
+Check the list of changed files against what was modified during this session, ensure they match expectations, then commit and push the changes.
 
 ### Process
 
@@ -40,31 +40,26 @@ Present the list of changed files for user review, ensure they match expectation
    ```
    Also run `git diff --stat` to see a summary of changes.
 
-2. **Present changes to the user for review**
+2. **Verify changes match expectations**
 
-   Use the AskUserQuestion tool to ask structured questions about the changes:
+   Compare the changed files against what you modified during this session:
+   - Do the modified files match what you edited?
+   - Are there any unexpected new files?
+   - Are there any unexpected deleted files?
+   - Do the line counts seem reasonable for the changes you made?
 
-   Show the user:
-   - List of modified files
-   - List of new files
-   - List of deleted files
-   - Summary of changes (lines added/removed)
+   If changes match expectations, proceed to commit.
 
-   Ask them to confirm:
-   - "Do these changed files match your expectations?"
-   - Provide options: "Yes, proceed with commit" / "No, let me review first" / "No, some files shouldn't be included"
+   If there are unexpected changes:
+   - Investigate why (e.g., lint auto-fixes, generated files)
+   - If they're legitimate side effects of your work, include them
+   - If they're unrelated or shouldn't be committed, use `git restore` to discard them
 
-3. **Handle user response**
-
-   - If user confirms, proceed to commit
-   - If user wants to review first, wait for them to come back
-   - If user says some files shouldn't be included, ask which files to exclude and use `git restore` or `git checkout` to unstage them
-
-4. **Stage all appropriate changes**
+3. **Stage all appropriate changes**
    ```bash
    git add -A
    ```
-   Or stage specific files if user excluded some.
+   Or stage specific files if some were excluded.
 
 5. **View recent commit messages for style reference**
    ```bash
@@ -93,8 +88,8 @@ Present the list of changed files for user review, ensure they match expectation
 
 ## Quality Criteria
 
-- Changed files list was presented to user
-- User explicitly confirmed the files match expectations
+- Changed files list was reviewed by the agent
+- Files match what was modified during this session (or unexpected changes were investigated and handled)
 - Commit message follows project conventions
 - Commit was created successfully
 - Changes were pushed to remote
@@ -102,7 +97,7 @@ Present the list of changed files for user review, ensure they match expectation
 
 ## Context
 
-This is the final step of the commit workflow. It ensures the user has reviewed and approved the changes before they are committed and pushed. This prevents accidental commits of unintended files or changes.
+This is the final step of the commit workflow. The agent verifies that the changed files match its own expectations from the work done during the session, then commits and pushes. This catches unexpected changes while avoiding unnecessary user interruptions.
 
 
 ### Job Context

{deepwork-0.3.0 → deepwork-0.3.1}/.gemini/skills/commit/index.toml

@@ -31,7 +31,7 @@ Steps:
    Command: `/commit:test`
 2. **lint** - Format and lint code with ruff using a sub-agent (requires: test)
    Command: `/commit:lint`
-3. **commit_and_push** - Review changed files, commit, and push to remote (requires: lint)
+3. **commit_and_push** - Verify changed files, commit, and push to remote (requires: lint)
    Command: `/commit:commit_and_push`
 
 ## Execution Instructions

{deepwork-0.3.0 → deepwork-0.3.1}/.gemini/skills/deepwork_rules/define.toml

@@ -275,10 +275,17 @@ 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:
@@ -286,6 +293,7 @@ Example use cases:
 - 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

{deepwork-0.3.0 → deepwork-0.3.1}/.gemini/skills/deepwork_rules/index.toml

@@ -17,10 +17,17 @@ 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:
@@ -28,6 +35,7 @@ Example use cases:
 - 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-0.3.0 → deepwork-0.3.1}/.gitignore

@@ -83,3 +83,8 @@ dmypy.json
 *.tmp
 .temp/
 tmp/
+
+# DeepWork runtime artifacts
+.deepwork/.last_work_tree
+.deepwork/.last_head_ref
+.deepwork/tmp/