bugfix-test

Run TypeScript and ESLint checks with optional Playwright UI validation for bugfixes.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/noni2she/agent-fix --skill bugfix-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugfix-test
Source: https://github.com/noni2she/agent-fix/tree/main/skills/bugfix-test
Command: npx skills add https://github.com/noni2she/agent-fix --skill bugfix-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams validate that an implemented bugfix is actually correct and does not introduce obvious regressions or unsafe side effects.

Core Features & Use Cases

  • Static TypeScript + ESLint gate: Runs the project’s TypeScript compile check and ESLint with clear PASS/FAIL semantics (errors fail, warnings allowed).
  • Strategy and code-quality compliance: Confirms the fix matches the strategy from analyze.md, checks diff signals like TODO refactor, and flags risky patterns such as console.log/debugger or large formatting changes.
  • Conditional behavior validation: Runs Playwright-based behavior scenarios only when the change is likely UI-relevant, using a strict observe-then-scenario design approach.

Quick Start

Run bugfix-test with the analyze report path and the implement report path produced by the previous pipeline phases.

Frequently Asked Questions about bugfix-test

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

FAQPage Schema
How do I verify a bugfix doesn't introduce regressions using git diff?

To verify a bugfix doesn't introduce regressions, this Skill analyzes git diff to assess side effects, checks strategy compliance from analyze.md, and runs TypeScript compile checks to enforce a strict PASS or FAIL gate.

How do I run ESLint and TypeScript validation for a bugfix?

You run ESLint and TypeScript validation by executing project-defined compile commands through this Skill, which applies clear semantics where errors fail the bugfix validation gate and warnings are allowed.

Does bugfix validation run Playwright behavior scenarios automatically?

Playwright behavior scenarios run conditionally during bugfix validation only when the git diff indicates the change is likely UI-relevant, following a strict observe-then-scenario design approach.

What static analysis patterns are flagged as risky in a bugfix?

Static analysis flags risky patterns in a bugfix by checking diff signals for TODO refactors, large formatting changes, and unsafe code like console.log or debugger statements to prevent side effects.

Do I need analyze.md and implement.md reports to validate a bugfix?

You need analyze.md and implement.md reports to validate a bugfix because this Skill uses these artifacts to determine compliance checks and evaluate whether the implementation matches the initial strategy.