scoped-tests

Étoiles104

Forks32

Mis à jour19 mai 2026 à 15:21

Use after changing code, before claiming work is done — run the test command scoped to what you changed instead of the whole suite, to avoid the timeout and context waste of full-suite runs on a small change.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

coleam00

coleam00/helpline

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	scoped-tests
description	Use after changing code, before claiming work is done — run the test command scoped to what you changed instead of the whole suite, to avoid the timeout and context waste of full-suite runs on a small change.

Scoped test runner

The article's rule: running the full suite when you changed one part of the codebase wastes context and time. Pick the narrowest command that still covers the change.

Changed one service / package / app? Run only that area's test command. The exact command lives in that area's CLAUDE.md — subdirectory CLAUDE.md files should specify the test command that applies to that part of the repo.
Changed shared / core code that other areas import? Run the full suite — a change there ripples everywhere, so a scoped run would miss regressions.
Not sure what a change reaches? Trace its importers first (the codebase-search MCP's find_references does this), then scope accordingly.

This skill is repo-agnostic on purpose: it carries the principle. The exact commands belong in each repo's own CLAUDE.md hierarchy, not bundled here.

Plus depuis ce dépôt

même dépôt

api-add-route

coleam00/helpline

Use when adding or changing an HTTP route under services/api. Walks the exact steps so the new route follows Helpline's gateway conventions.

2026-05-19104

billing-money-rules

coleam00/helpline

Use when creating or editing code under services/billing. Enforces Helpline's money-handling rules — integer cents only, seat limits, and BillingError for every violation.

2026-05-19104

scoped-tests

coleam00/helpline

Use after changing code, before claiming work is done — picks the correctly scoped pytest command instead of running the whole suite. Helps avoid the timeout-and-context-waste of full-suite runs on a one-service change.

2026-05-19104

name	scoped-tests
description	Use after changing code, before claiming work is done — run the test command scoped to what you changed instead of the whole suite, to avoid the timeout and context waste of full-suite runs on a small change.

Scoped test runner

The article's rule: running the full suite when you changed one part of the codebase wastes context and time. Pick the narrowest command that still covers the change.

Changed one service / package / app? Run only that area's test command. The exact command lives in that area's CLAUDE.md — subdirectory CLAUDE.md files should specify the test command that applies to that part of the repo.
Changed shared / core code that other areas import? Run the full suite — a change there ripples everywhere, so a scoped run would miss regressions.
Not sure what a change reaches? Trace its importers first (the codebase-search MCP's find_references does this), then scope accordingly.

This skill is repo-agnostic on purpose: it carries the principle. The exact commands belong in each repo's own CLAUDE.md hierarchy, not bundled here.