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.

Jump to install

Repository: tomevault-io/skills-registry
Last source activity: July 3, 2026 at 19:45
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

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

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

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 */