Agent skill
python3-bug
Debug functional issues in Python code using specs, logs, and observed behavior. Use when a feature isn't working as specified, when investigating runtime errors, or when scoping a problem before implementing a fix.
Install this agent skill to your Project
npx add-skill https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/python3-development/skills/python3-bug
SKILL.md
<problem_description>$ARGUMENTS</problem_description>
Python Functional Bug Investigation
The model investigates functional bugs using specifications, logs, and observed behavior to scope the problem before implementing fixes.
Arguments
<problem_description/>
Instructions
Consult ../python3-development/references/python3-standards.md when applying shared architecture, typing, testing, or CLI rules; full standards, graphs, and amendment process are documented there.
- Gather context from user (spec, logs, reproduction steps)
- Scope the problem (what works, what doesn't, boundaries)
- Form hypotheses about root cause
- Investigate systematically with evidence
- Propose fix only after understanding root cause
Phase 1: Problem Intake
Required Information
Ask for these if not provided:
SPECIFICATION
- [ ] What should the feature do? (spec, user story, acceptance criteria)
- [ ] What behavior is expected?
OBSERVED BEHAVIOR
- [ ] What actually happens?
- [ ] Error messages (exact text)
- [ ] Logs (relevant sections)
REPRODUCTION
- [ ] Steps to reproduce
- [ ] Input data that triggers the bug
- [ ] Environment (Python version, OS, dependencies)
CONTEXT
- [ ] When did it last work? (if ever)
- [ ] What changed recently?
- [ ] Is it intermittent or consistent?
Intake Template
## Bug Report
**Expected Behavior**:
[What should happen according to spec]
**Actual Behavior**:
[What is happening]
**Error/Logs**:
[Paste exact error messages or relevant log output]
**Reproduction Steps**:
1. [First step]
2. [Second step]
3. [Step where failure occurs]
**Environment**:
- Python: [version]
- OS: [os]
- Relevant packages: [list]
**Recent Changes**:
[What changed before this started happening]
Phase 2: Problem Scoping
Define Boundaries
Establish what works and what doesn't:
WORKING
- [ ] [Feature X works correctly]
- [ ] [Feature Y works correctly]
NOT WORKING
- [ ] [Feature Z fails with error]
- [ ] [Feature W produces wrong output]
UNKNOWN
- [ ] [Feature V not tested yet]
Narrow the Scope
Questions to answer:
1. Is this a regression or never worked?
2. Does it fail for all inputs or specific ones?
3. Does it fail in all environments or specific ones?
4. Is the failure consistent or intermittent?
5. What's the smallest reproduction case?
Create Minimal Reproduction
# Minimal reproduction case
# Goal: Smallest code that demonstrates the bug
def test_reproduction():
"""Minimal reproduction of the bug."""
# Setup
input_data = {"key": "value"} # Specific input that triggers bug
# Action
result = buggy_function(input_data)
# Expected vs Actual
assert result == expected, f"Got {result}, expected {expected}"
Phase 3: Hypothesis Formation
Generate Hypotheses
Based on symptoms, form multiple hypotheses:
## Hypothesis List
H1: [Description of potential cause]
Evidence for: [what supports this]
Evidence against: [what contradicts this]
Test: [how to verify]
H2: [Description of potential cause]
Evidence for: [what supports this]
Evidence against: [what contradicts this]
Test: [how to verify]
H3: [Description of potential cause]
Evidence for: [what supports this]
Evidence against: [what contradicts this]
Test: [how to verify]
Common Bug Categories
| Category | Symptoms | Investigation |
|---|---|---|
| Type Error | AttributeError, TypeError | Check types at boundary |
| State Mutation | Intermittent, order-dependent | Look for shared mutable state |
| Race Condition | Intermittent, timing-dependent | Check async/threading code |
| Edge Case | Specific inputs fail | Test boundary conditions |
| Integration | Works in isolation, fails together | Check interface contracts |
| Configuration | Environment-dependent | Compare working vs failing env |
Phase 4: Systematic Investigation
Tracing Approach
Follow the data flow:
1. INPUT: What data enters the function?
- Log: input values, types, shapes
2. PROCESSING: What transformations occur?
- Add debug logging at each step
- Check intermediate values
3. OUTPUT: What comes out?
- Compare actual vs expected output
- Check return type and structure
4. SIDE EFFECTS: What else changes?
- Database writes
- File system changes
- External API calls
- Global state modifications
Debug Logging Pattern
import logging
logger = logging.getLogger(__name__)
def investigate_function(data: InputType) -> OutputType:
logger.debug(f"INPUT: data={data!r}, type={type(data)}")
# Step 1
intermediate1 = process_step1(data)
logger.debug(f"STEP1: intermediate1={intermediate1!r}")
# Step 2
intermediate2 = process_step2(intermediate1)
logger.debug(f"STEP2: intermediate2={intermediate2!r}")
# Step 3
result = process_step3(intermediate2)
logger.debug(f"OUTPUT: result={result!r}, type={type(result)}")
return result
Hypothesis Testing
For each hypothesis:
def test_hypothesis_1():
"""Test H1: [hypothesis description]"""
# Setup to isolate this hypothesis
# ...
# Action that should reveal if H1 is correct
# ...
# Assertion that confirms or refutes H1
# If this passes, H1 is likely correct
# If this fails, H1 is refuted
Phase 5: Root Cause Analysis
Evidence Collection
## Root Cause Evidence
**Confirmed Root Cause**: [description]
**Evidence**:
1. [File:line] - [what this shows]
2. [Log entry] - [what this shows]
3. [Test result] - [what this shows]
**Why This Causes the Bug**:
[Explanation of the causal chain from root cause to symptom]
**Eliminated Hypotheses**:
- H2: Ruled out because [evidence]
- H3: Ruled out because [evidence]
Fix Requirements
Before implementing fix:
## Fix Specification
**Root Cause**: [concise description]
**Location**: [file:line range]
**Fix Approach**:
[Description of what needs to change]
**Risks**:
- [Potential side effect 1]
- [Potential side effect 2]
**Test Coverage**:
- [ ] Test for original bug (regression test)
- [ ] Test for edge cases
- [ ] Test for potential side effects
Phase 6: Fix Implementation
Fix Checklist
BEFORE FIX
- [ ] Root cause identified with evidence
- [ ] Minimal reproduction exists
- [ ] Test coverage plan created
DURING FIX
- [ ] Fix addresses root cause (not symptoms)
- [ ] Fix is minimal (no scope creep)
- [ ] Regression test written first
AFTER FIX
- [ ] Regression test passes
- [ ] Existing tests still pass
- [ ] Edge case tests added
- [ ] Code review if significant change
Regression Test Pattern
def test_bug_12345_description():
"""Regression test for bug #12345.
Bug: [brief description of the original bug]
Root cause: [what was wrong]
Fix: [what was changed]
"""
# Arrange: Setup that triggered the bug
input_data = create_problematic_input()
# Act: The operation that failed
result = fixed_function(input_data)
# Assert: Verify correct behavior
assert result == expected_output
# Also verify the specific fix worked
assert result.specific_field == expected_value
Investigation Report Format
## Bug Investigation Report
**Issue**: [Brief description]
**Status**: [Investigating | Root Cause Found | Fixed | Cannot Reproduce]
### Problem Statement
**Expected**: [spec behavior]
**Actual**: [observed behavior]
**Impact**: [who/what is affected]
### Investigation Timeline
1. [timestamp] - [action taken] - [result]
2. [timestamp] - [action taken] - [result]
3. [timestamp] - [action taken] - [result]
### Hypotheses
| # | Hypothesis | Status | Evidence |
|---|------------|--------|----------|
| H1 | [description] | Confirmed/Refuted | [evidence] |
| H2 | [description] | Confirmed/Refuted | [evidence] |
### Root Cause
**Location**: [file:line]
**Description**: [what's wrong and why]
**Evidence**: [how we know this is the cause]
### Fix
**Approach**: [what will be changed]
**Files Modified**: [list]
**Tests Added**: [list]
### Verification
- [ ] Bug no longer reproduces
- [ ] Regression test passes
- [ ] Existing tests pass
- [ ] Edge cases covered
Common Python Bug Patterns
NoneType Errors
# Bug: AttributeError: 'NoneType' has no attribute 'x'
# Cause: Function returns None unexpectedly
# Investigation
result = get_something()
print(f"result is None: {result is None}") # Check this first
# Fix: Add proper None handling
if (result := get_something()) is None:
raise ValueError("Expected result but got None")
return result.x
Mutable Default Arguments
# Bug: List accumulates across calls
def buggy(items=[]): # WRONG: mutable default
items.append(1)
return items
# Fix
def fixed(items: list | None = None) -> list:
if items is None:
items = []
items.append(1)
return items
Async/Await Issues
# Bug: Coroutine never executed
async def fetch_data():
return await api_call()
# WRONG: Missing await
result = fetch_data() # Returns coroutine, not result
# Fix
result = await fetch_data()
Import Errors
# Bug: ImportError or circular import
# Investigation: Check import order and dependencies
# Fix: Use local imports for circular dependencies
def function_that_needs_other_module():
from .other_module import OtherClass # Local import
return OtherClass()
References
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ccc
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the index', 'ccc', 'cocoindex-code'.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
delegate
Quick delegation template for sub-agent prompts. Use when assigning work to a sub-agent, before invoking the Agent tool, or when preparing prompts for specialized agents. Provides the WHERE-WHAT-WHY framework. For comprehensive delegation guidance, activate the agent-orchestration how-to-delegate skill.
swarm-spawning
Spawn agents and teammates in Claude Code swarms. Use when choosing between subagents vs teammates, selecting agent types (Explore, Plan, general-purpose, plugin agents), configuring spawn backends (in-process, tmux, iterm2), or setting environment variables for spawned agents.
knowledge-explorer
Manage the research/ knowledge base (KB) of tool and library research entries. Use when browsing KB topics, adding new research entries, updating existing entries with dated revisions, fetching GitHub repo metadata into a draft KB entry, or migrating old-format entries to skill-spec frontmatter. Triggers on tasks like "what do we have on X", "add this to the KB", "update the KB entry for Y", "fetch github info for owner/repo", or "migrate old entries".
design-anti-patterns
Enforce anti-AI UI design rules based on the Uncodixfy methodology. Use when generating HTML, CSS, React, Vue, Svelte, or any frontend UI code. Prevents "Codex UI" — the generic AI aesthetic of soft gradients, floating panels, oversized rounded corners, glassmorphism, hero sections in dashboards, and decorative copy. Applies constraints from Linear/Raycast/Stripe/GitHub design philosophy: functional, honest, human-designed interfaces. Triggers on: UI generation, dashboard building, frontend component creation, CSS styling, landing page design, or any task producing visual interface code.
Didn't find tool you were looking for?