Smart Scoped Test Runner

Run tests only for scopes affected by current changes. Scope names can be provided via $ARGUMENTS or auto-detected from git diff.

Scope Dependency Graph

packages/core ──→ packages/agent ──→ packages/process
    │              │
    ├──→ packages/api ┘
    ├──→ packages/bot
    ├──→ packages/sysadmin-api
    ├──→ packages/backup
    └──→ packages/pipeline

Step 1: Detect Affected Scopes

If $ARGUMENTS specifies scope names (e.g., packages/api packages/agent), use those directly. Otherwise auto-detect:

1. Run git diff --name-only HEAD to list staged + unstaged changed files
2. Map each changed file to its scope by extracting the first path component
3. Valid scopes: packages/core, packages/agent, packages/api, packages/bot, packages/pipeline, packages/process, packages/sysadmin-api, packages/backup, packages/web, packages/sysadmin-web
4. Ignore files not in a valid scope (e.g., root configs, docs)

Expected output: A list like Detected affected scopes: packages/core, packages/api

Step 2: Expand Downstream Dependencies

Add downstream scopes that depend on any changed scope:

• packages/core changed → add ALL other scopes (it is the foundation)
• packages/agent changed → also add packages/process (process depends on agent)

Step 3: Run Tests in Dependency Order

Execute make test in each affected scope's directory, following this order:

1. packages/core (foundation — test first)
2. packages/agent
3. packages/pipeline
4. packages/process (depends on agent)
5. packages/api
6. packages/bot
7. packages/sysadmin-api, packages/backup
8. packages/web / packages/sysadmin-web — run make -C <scope> pr-ready (ESLint, no pytest for frontend)

Skip scopes not in the affected set. If a scope fails, continue running remaining scopes to collect all failures.

Step 4: Report Results

Produce a summary table:

Examples

• /test-scope — Auto-detect from git diff and run all affected
• /test-scope packages/api — Run tests only for packages/api
• /test-scope packages/core — Run tests for packages/core AND all downstream scopes
• /test-scope packages/agent packages/api — Run tests for both specified scopes

Troubleshooting

• "No changes detected": Ensure you have uncommitted changes. Run git status to verify.
• "make test fails with ModuleNotFoundError": Dependencies may not be installed. Run uv sync --all-packages from the workspace root.
• Root make test runs every Python scope plus check-env; this skill runs only the affected scopes via make -C <scope> test.
• Agent/API tests that need NATS or the API require the Docker dev stack, and no locally running agent of the same class (it shares the test runner's queue group and eats its events).
• Frontend scopes: packages/web and packages/sysadmin-web have no tests — make -C <scope> pr-ready runs ESLint instead.