repo-testing

Estrellas0

Forks0

Actualizado13 de abril de 2026 a las 06:24

Write, repair, or stabilize tests in this Go repository. Use when adding unit tests, reproducing bugs with tests, fixing failing or flaky tests, updating testdata, or improving coverage for changed behavior.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

atframework

atframework/atdtool

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	repo-testing
description	Write, repair, or stabilize tests in this Go repository. Use when adding unit tests, reproducing bugs with tests, fixing failing or flaky tests, updating testdata, or improving coverage for changed behavior.

Repo testing

Reproduce with the smallest scope possible first: package, file, or -run target.
For bug fixes, prefer adding or updating the failing test before the code fix.
Prefer table-driven tests for precedence, parser variants, and configuration matrices.
Use t.TempDir(), filepath.Join, isolated temp files, and deterministic fixtures.
Avoid shared temp paths, random sleeps, and hidden global state.
Keep testdata/ compact, readable, and close to the package under test.
Close files before cleanup; Windows failures often come from open handles.
After focused tests pass, widen verification as needed and finish with go test ./... when appropriate.

Más de este repositorio

mismo repositorio

cli-command-change-checklist

atframework/atdtool

Review or implement user-visible CLI command changes in this repository. Use when changing subcommands, flags, help text, defaults, output paths, or command behavior.

2026-04-130

docs-sync-after-code-change

atframework/atdtool

Synchronize documentation after code changes in this repository. Use when implementation changes affect commands, values precedence, template runtime behavior, project structure docs, or examples.

2026-04-130

helm-values-precedence-review

atframework/atdtool

Review or change Helm/chart values precedence in this repository. Use when working on global.yaml, chart-name yaml, modules, runtime values, template overrides, or --set merge behavior.

2026-04-130

repo-implementation

atframework/atdtool

Implement or refactor production code in this Go repository. Use when adding features, fixing bugs, changing CLI behavior, or modifying files under cmd/, cli/, internal/, pkg/, or logarchive/.

2026-04-130

name	repo-testing
description	Write, repair, or stabilize tests in this Go repository. Use when adding unit tests, reproducing bugs with tests, fixing failing or flaky tests, updating testdata, or improving coverage for changed behavior.

Repo testing

Reproduce with the smallest scope possible first: package, file, or -run target.
For bug fixes, prefer adding or updating the failing test before the code fix.
Prefer table-driven tests for precedence, parser variants, and configuration matrices.
Use t.TempDir(), filepath.Join, isolated temp files, and deterministic fixtures.
Avoid shared temp paths, random sleeps, and hidden global state.
Keep testdata/ compact, readable, and close to the package under test.
Close files before cleanup; Windows failures often come from open handles.
After focused tests pass, widen verification as needed and finish with go test ./... when appropriate.