ReddRadar
Agent skill
debug
Use when debugging Python failures using a structured investigation workflow focused on reproduction, boundary assumptions, and root-cause isolation. Activate for tracebacks, test failures, or unexpected behavior.
Install this agent skill to your Project
npx add-skill https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/python-engineering/skills/debug
SKILL.md
Debug
Structured debugging flow.
Input
Symptom: $ARGUMENTS
Investigation Steps
- Restate the observed symptom — exact error message, stack trace, or unexpected behavior
- Identify the smallest reproducible scope — minimal code that triggers the failure
- Isolate assumptions — environment, input, state, concurrency
- Inspect boundaries early — check validation and conversion points where external data enters
- Distinguish implementation bugs from test bugs — dual-hypothesis approach
- Verify the fix — rerun deterministic checks after fixing
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 |
Debug Logging Pattern
import logging
logger = logging.getLogger(__name__)
def investigate(data: InputType) -> OutputType:
logger.debug(f"INPUT: {data!r}, type={type(data)}")
intermediate = step1(data)
logger.debug(f"STEP1: {intermediate!r}")
result = step2(intermediate)
logger.debug(f"OUTPUT: {result!r}, type={type(result)}")
return result
Output Format
## Bug Investigation Report
**Status**: [Investigating | Root Cause Found | Fixed | Cannot Reproduce]
### Root Cause
**Location**: file:line
**Description**: what's wrong and why
**Evidence**: how we know
### Fix
**Approach**: what was changed
**Regression Test**: test for the original bug
**Verification**: all checks pass after fix
Checks After Fix
uv run ruff check
uv run pytest -v
uv run ty check # or project checker
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
Jamie-BitFlight/claude_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'.
Jamie-BitFlight/claude_skills
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.
Jamie-BitFlight/claude_skills
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.
Jamie-BitFlight/claude_skills
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.
Jamie-BitFlight/claude_skills
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".
Jamie-BitFlight/claude_skills
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?