issue-to-regression-test

Use this skill when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix. This skill will guide you through fetching the issue details, scaffolding a standard regression test, writing a failing test, fixing the issue, and verifying that all tests pass. Make sure to use this skill whenever a bug fix is requested.

Ir a la instalación

Repositorio: tomevault-io/skills-registry
Última actividad en el origen: 3 de julio de 2026 a las 19:45
Idioma detectado de SKILL.md: inglés
Estrellas: 0
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

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.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/tomevault-io/skills-registry --skill issue-to-regression-test

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

2 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

Issue to Regression Test

This skill automates the workflow of fixing a bug reported via a GitHub issue by creating a regression test first.

Workflow

Scaffold the Regression Test:

If an issue number is provided, use the bundled Node.js script to scaffold the test file.
Command: node .agents/skills/issue-to-regression-test/scripts/scaffold-test.js <issue_number>
This script will automatically fetch issue details using gh and create a file in src/tests/ with the correct JSDoc header.

Refine and Reproduce the Bug:

Open the newly created test file in src/tests/.
Implement a test case that fails when run against the current codebase.
The test should accurately reflect the bug described in the issue.
Use vitest for testing. Import describe, expect, it from vitest.
Import necessary modules from src/ to test the failing behavior.

Fix the Bug:

Modify the source code in the src/ directory to fix the reported bug.
Aim for a surgical fix that solves the problem without unnecessary refactoring.

Verify Fix and Prevent Regressions:

Ensure the new test passes.
Run ALL tests in the project to ensure no regressions were introduced.
Command: npx vitest run

Example JSDoc

/** * Regression test for issue #2: Visibility settings from template are not respected * https://github.com/brunosabot/streamline-card/issues/2 * * Bug: When configuring visibility in a template, the card would always be visible * instead of respecting the visibility conditions. * * Expected: Visibility settings from templates should be properly applied to the card */