How do I install the Test Scope skill?

Run npx skillmds@latest add glitterkill/test-scope in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Test Scope safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Test Scope?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Test Scope free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Test Scope?

GlitterKill (@glitterkill) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Test Scope by glitterkill — Agent Skill

Name: Test Scope
Rating: 4.2 (5 reviews)
Author: GlitterKill

File contents

Targeted Test Runner

Analyze recent code changes to determine which test suites need to run, then execute only those.

Test Suite Map

Source Path Pattern	Test Suite	Run Command
`src/indexer/`, `src/indexer/adapter/`	Adapter harness	`npm run test:harness`
`src/mcp/tools/**`, `src/server.ts`	Golden snapshots	`npm run test:golden`
`src/code/skeleton*`	Skeleton determinism	`node --import tsx --test tests/skeleton-determinism.test.ts`
`src/graph/`, `src/delta/`	Slice/blast radius	`node --import tsx --test tests/slice-cache.test.ts tests/blastRadius.test.ts`
`src/mcp/`, `src/db/`, `src/config/**`	Unit tests	`npm test`
`native/**`	Native parity	`npm run test:native-parity`
`tests/property/**`	Property tests	`node --import tsx --test tests/property/*.test.ts`
Any `*.ts` in `src/`	Typecheck	`npm run typecheck`

Steps

Detect changed files:
```
git diff --name-only HEAD
git diff --name-only --cached
```
If no uncommitted changes, use git diff --name-only HEAD~1 instead.
Map changes to test suites using the table above. A single change can trigger multiple suites.
Always run typecheck if any .ts file in src/ changed.

Report the plan before running:

Changed files: 3
Affected suites: typecheck, golden snapshots, unit tests
Skipping: adapter harness, native parity, property tests, stress tests

Execute the affected suites sequentially. Use sdl.workflow with runtimeExecute if SDL-MCP is running, otherwise use Bash directly.
Report results with pass/fail status for each suite.

Rules

If changes touch package.json, tsconfig.json, or eslint.config.mjs, run the full suite (npm test)
If changes touch only .md, .json (non-package), or config files, skip all test suites and report "No code changes — tests not needed"
Never run test:stress or test:mutation automatically — those are opt-in only
Run npm run build:all before any test suite that reads from dist/

---name: test-scopedescription: Determine which test suites are affected by recent code changes and run only the relevant ones. Avoids running the full test matrix when only specific areas changed.---# Targeted Test RunnerAnalyze recent code changes to determine which test suites need to run, then execute only those.## Test Suite Map| Source Path Pattern | Test Suite | Run Command ||---|---|---|| `src/indexer/**`, `src/indexer/adapter/**` | Adapter harness | `npm run test:harness` || `src/mcp/tools/**`, `src/server.ts` | Golden snapshots | `npm run test:golden` || `src/code/skeleton*` | Skeleton determinism | `node --import tsx --test tests/skeleton-determinism.test.ts` || `src/graph/**`, `src/delta/**` | Slice/blast radius | `node --import tsx --test tests/slice-cache.test.ts tests/blastRadius.test.ts` || `src/mcp/**`, `src/db/**`, `src/config/**` | Unit tests | `npm test` || `native/**` | Native parity | `npm run test:native-parity` || `tests/property/**` | Property tests | `node --import tsx --test tests/property/*.test.ts` || Any `*.ts` in `src/` | Typecheck | `npm run typecheck` |## Steps1. **Detect changed files**: ```bash git diff --name-only HEAD git diff --name-only --cached ``` If no uncommitted changes, use `git diff --name-only HEAD~1` instead.2. **Map changes to test suites** using the table above. A single change can trigger multiple suites.3. **Always run typecheck** if any `.ts` file in `src/` changed.4. **Report the plan** before running: ``` Changed files: 3 Affected suites: typecheck, golden snapshots, unit tests Skipping: adapter harness, native parity, property tests, stress tests ```5. **Execute the affected suites** sequentially. Use `sdl.workflow` with `runtimeExecute` if SDL-MCP is running, otherwise use Bash directly.6. **Report results** with pass/fail status for each suite.## Rules- If changes touch `package.json`, `tsconfig.json`, or `eslint.config.mjs`, run the full suite (`npm test`)- If changes touch only `.md`, `.json` (non-package), or config files, skip all test suites and report "No code changes — tests not needed"- Never run `test:stress` or `test:mutation` automatically — those are opt-in only- Run `npm run build:all` before any test suite that reads from `dist/`

Frequently asked questions

Test Scope