Scoped Tests
- 1 installs
- 108 repo stars
- Updated May 20, 2026
- coleam00/helpline
Picks the narrowest pytest command that still covers a change instead of running the full Helpline suite, to save time and context.
About
Maps each changed service or package to the correctly scoped pytest command, running the full suite only for shared packages/core and packages/db. A developer uses it after a change, before claiming work is done.
- Per-service test command mapping table
- Changes in packages/core or packages/db always run the full suite
Scoped Tests by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,747 of 2,155 Testing & QA skills by installs in the Skillselion catalog
- Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/coleam00/helpline --skill scoped-testsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 108 |
| Last updated | May 20, 2026 |
| Repository | coleam00/helpline ↗ |
What it does
Picks the narrowest pytest command that still covers a change instead of running the full Helpline suite, to save time and context.
Files
Scoped test runner
The article's rule: running the full suite on a one-service change wastes context and time. Pick the narrowest command that still covers the change.
| What you changed | Run |
|---|---|
services/auth/** | uv run pytest services/auth tests/test_auth.py |
services/billing/** | uv run pytest services/billing tests/test_billing.py |
services/api/** | uv run pytest services/api tests/test_api.py |
services/notifications/** | uv run pytest services/notifications |
services/search/** | uv run pytest services/search |
packages/core/** or packages/db/** | uv run pytest -q (FULL — these are imported everywhere) |
Rule: a change in packages/core or packages/db always runs the full suite. A change in a single service runs only that service plus its test file.
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3k