Stats
Actions
Tags
From dev-toolbox
Show which Turborepo packages in spa/ are affected by current changes compared to main. Skips if turborepo stack is not enabled.
How this command is triggered — by the user, by Claude, or both
Slash command
/dev-toolbox:affectedFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
Show which spa/ packages are affected by current changes versus `main`.
## Pre-check
Read the CLAUDE.md stack manifest. If `turborepo` is not enabled, print:
and exit. Otherwise:
## Steps
1. **Show affected packages**:
2. **Show changed files by package**:
3. **Summarise**:
- List affected packages and why (direct changes vs dependency cascade).
- Suggest test commands for affected packages:
- `cd spa && pnpm run -F <package> test` for each affected package with tests.
- Flag if shared packages (`@repo/ui`, `@repo/hooks`, `@repo/utils`, `@repo/api`, `@repo/env...Show which spa/ packages are affected by current changes versus main.
Read the CLAUDE.md stack manifest. If turborepo is not enabled, print:
turborepo stack not enabled in manifest — skipping /affected.
and exit. Otherwise:
Show affected packages:
cd spa && pnpm turbo run build --dry --filter=...[origin/main...HEAD] 2>&1
Show changed files by package:
git diff origin/main...HEAD --stat
Summarise:
cd spa && pnpm run -F <package> test for each affected package with tests.@repo/ui, @repo/hooks, @repo/utils, @repo/api, @repo/env) were modified — those cascade to downstream consumers.dotnet test always runs the full solution)./check.npx claudepluginhub tk-kamyk/dev-tools --plugin dev-toolbox/affectedDetects directly and transitively affected packages in monorepos from git changes, outputs lists with changed file counts and recommended build/test/lint/deploy commands.