bug

Generates a root-cause bug spec and applies the approved fix with a regression test.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill bug-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/bug
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill bug-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fixing confirmed bugs through a full feature-design workflow is slow and heavy. This Skill provides a lightweight one-approval flow that produces a trimmed Root Cause / Fix / Regression Test spec, then applies the fix — without bypassing governance controls. ## Core Features & Use Cases - One-screen Bug Spec: Drafts a concise spec covering symptom, expected behaviour, root-cause hypothesis, files involved, fix approach, and regression test, gated behind a single APPROVED / EDIT / REJECT cycle. - Governed fix application: Persists the approved spec to docs/Release{R}/Sprint{S}/UserStory{ID}/ before touching source, applies a per-file source-read consent gate, and writes the minimal fix plus a regression test. - Scope guardrails: Redirects anything requiring new endpoints, schema changes, or design decisions to the full ICEA feature flow. - Use Case: A developer runs /bug ADO-2341 "Filter crashes when user has no roles", approves the drafted spec, and gets the null-guard fix plus a regression test filed alongside the Azure DevOps work item. ## Quick Start Run /bug with an Azure DevOps bug ID and a one-line description, for example /bug ADO-2341 "Filter crashes when user has no roles", then approve the drafted spec.

Frequently Asked Questions about bug

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

FAQPage Schema
How do I fix a bug with a lightweight approval workflow?

Invoke /bug with an Azure DevOps bug ID and a one-line description. The Skill drafts a one-screen spec with symptom, root-cause hypothesis, fix approach, and regression test; once you reply APPROVED, it applies the minimal fix and writes the test.

When should I use /bug instead of a full feature spec?

Use /bug only for confirmed defects in existing behaviour such as null references, broken logic, or UI glitches. Anything requiring a new endpoint, schema change, new component, or design decision must go through the full ICEA feature flow instead.

Does the bug fix workflow require a regression test?

Yes, a regression test is mandatory. The spec must name one specific given/when/then test case, and the fix is not considered complete until that test is written or updated in the established test file.

Why does the bug spec get saved before any code is written?

A PreToolUse hook blocks writes to guarded source files unless an approved spec exists under docs/. Saving the approved .bugspec.md file first satisfies that floor so the subsequent fix writes are permitted.

Can the bug skill read source files before approval?

No. Source files are never opened before the spec is approved. After approval, each file listed in the spec still requires an individual consent confirmation before it is read.