ClaudeSuperPower
SubmitLog in

test-first-bugs

Skill

This skill should be used when the user reports a bug, describes unexpected behavior, says something is "broken", "not working", "failing", mentions an "error", "issue", or "problem" in code, or asks to "fix" something. Enforces test-driven bug fixing workflow.

0Automation

Install

git clone https://github.com/jamditis/claude-skills-journalism.git ~/.claude/skills/test-first-bugs

What is test-first-bugs?

This skill should be used when the user reports a bug, describes unexpected behavior, says something is "broken", "not working", "failing", mentions an "error", "issue", or "problem" in code, or asks to "fix" something. Enforces test-driven bug fixing workflow.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~65 tokens of context used while enabled, before you invoke anything

Documentation

README · ~4 min read

Test-first bug fixing

Enforce a disciplined bug-fixing workflow that prevents regression and parallelizes fix attempts.

Core workflow

When a bug is reported, follow these steps in order:

Phase 1: Reproduce and document

  1. Understand the bug — Gather details about expected vs actual behavior
  2. Identify the test location — Determine where tests live in the project (check for tests/, __tests__/, spec/, *.test.*, *.spec.* patterns)
  3. Write a failing test — Create a test that demonstrates the bug

Phase 2: Fix with subagents

  1. Launch fix subagents — Use the Task tool with subagent_type=general-purpose to attempt fixes

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.