scoped-tests

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.

Ir para a instalação

Repositório: coleam00/helpline
Última atividade na origem: 19 de maio de 2026 às 15:21
Idioma detectado do SKILL.md: inglês
Estrelas: 110
Forks: 35

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/coleam00/helpline --skill scoped-tests

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

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.

Voltar à pesquisa Voltar à instalação

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.

scoped-tests

Informações da origem

Opções de instalação

Revise os arquivos de origem

Scoped test runner

Mais deste repositório

Mais deste repositório

Scoped test runner