speckit-bug-test

Validates that a recorded bug fix resolves the reported issue and writes a verification report.

Updated May 28, 2026
One-click install
npx skills add https://github.com/whw23/PingoGate --skill speckit-bug-test-whw23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-bug-test
Source: https://github.com/whw23/PingoGate/tree/main/.claude/skills/speckit-bug-test
Command: npx skills add https://github.com/whw23/PingoGate --skill speckit-bug-test-whw23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a bug fix is applied, teams often lack a structured way to confirm the fix actually resolves the original symptom without introducing regressions. This Skill closes that gap by re-running reproduction steps and test suites, then recording a formal verification report. ## Core Features & Use Cases - Fix Verification: Re-runs the original reproduction steps and the tests added by the fix to confirm the bug is resolved. - Regression Checking: Executes existing test suites, lint, and type-checks to detect side effects from the fix. - Structured Reporting: Writes a verification report to .specify/bugs/<slug>/test.md with a verdict of verified, partial, or failed. - Use Case: After running a bug-fix workflow on a login timeout issue, invoke this Skill to re-execute the reproduction steps and regression suite, producing an auditable report that decides whether to close, hold, or reopen the bug. ## Quick Start Ask the assistant to validate the fix for the bug with slug login-timeout and generate the verification report.

Frequently Asked Questions about speckit-bug-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a bug fix actually works?▼

Re-run the original reproduction steps from the bug assessment, execute the tests added by the fix, and run the broader regression suite. This Skill automates that process and records the outcome in a test.md verification report.

How to test a bug fix in a spec-kit project?▼

Provide the bug slug or let the Skill resolve it from context or the .specify/bugs directory. It reads assessment.md and fix.md, plans and runs validation checks, then writes the verdict to .specify/bugs/<slug>/test.md.

What happens if the bug fix verification fails?▼

The report is marked failed when the symptom still reproduces or the fix breaks the regression suite. The Skill then recommends re-running the bug assessment workflow with the new evidence captured in test.md.

Does bug fix verification modify source code?▼

No. The Skill only runs checks and writes inside .specify/bugs/<slug>/. It never edits source code, and it refuses to overwrite an existing test.md without explicit confirmation.

When is a fix marked partial instead of verified?▼

A fix is marked partial when the original symptom is gone but unrelated regressions appear, some checks are inconclusive, or the reproduction could not actually be exercised, such as when it requires a production environment.