Debug
Systematically debug app issues by examining logs, database state, and git history
What You Can Do
You can systematically investigate application failures by examining logs, querying database state, and reviewing git history to identify root causes. This skill helps you understand the current state of your system without making changes, providing the contextual foundation needed to solve bugs efficiently during manual testing or implementation work.
Features
automatically locate and parse application logs from common directories to identify error patterns and stack traces
query SQLite databases and check database configuration to understand data consistency and state issues
review current branch, recent commits, and uncommitted changes to correlate code changes with observed problems
verify running processes and listening ports to diagnose connectivity and service availability issues
analyze plan/ticket files to align debugging investigation with intended test cases or implementation goals
cross-reference logs, database state, and git changes to identify patterns and root causes
gather all diagnostic information without modifying files or system state
Example Output
Example 1: Database Query Issue
I found the issue! Looking at the logs, there's a SQL syntax error at 2024-01-15 14:32:18. The recent commit (abc123) changed the query structure. Checking the database state, the `users` table is missing the `status` column that the new query expects. The migration appears to be uncommitted in your working directory.
Example 2: Service Connectivity Problem
The service logs show connection refused errors. Running `lsof -i :5432`, the database isn't listening on port 5432. Git history shows the database configuration changed 3 commits ago from localhost to 127.0.0.1. The process list shows the database service isn't running—likely crashed during startup due to the configuration change.
What's Included
- SKILL.md: Core debugging instruction set with investigation process
- Debugging checklist: Systematic steps for logs, database, and git examination
- Common log locations reference: Default paths for application logs across systems
- SQL query templates: Pre-built queries for common database state investigations
- Git command reference: Quick commands for branch, commit, and change analysis
Who It's For
- Backend engineers — debugging application failures and service issues during development
- QA/test engineers — investigating test failures and understanding failure root causes
- Full-stack developers — correlating frontend errors with backend state and logs
- DevOps engineers — diagnosing service and deployment issues
- Implementation specialists — troubleshooting issues during feature rollout or integration work
Best For
- Failure investigation — understanding why tests or features are failing
- Production troubleshooting — diagnosing live issues without making changes
- State verification — checking database consistency and service status
- Change correlation — identifying which code changes caused problems
- Debugging session bootstrap — gathering complete context before implementing fixes
You might also like
This skill maps construction claims as interdependent probability states rather than isolated analyses, allowing you to evaluate how changes in one contractual interpretation cascade through damages calculations, delay causation, and liability allocation. You can simultaneously model competing scenarios—concurrent causation, ambiguous change order triggers, insurance coverage dependencies—and identify which settlement positions minimize exposure across all correlated outcomes, not just single interpretations.
by parcadei
You'll transform high-level feature requirements into a complete development plan covering API design, frontend implementation, testing strategy, and documentation. The skill helps you identify dependencies, parallelize work across frontend and backend teams, and establish quality gates that ensure features ship bug-free with proper error handling and logging.
You'll follow the strict TDD workflow: write a failing test that defines expected behavior, verify it fails, write minimal production code to pass the test, then refactor for quality. This approach ensures complete test coverage, catches bugs early, and produces well-designed code backed by comprehensive test suites. Claude guides you through each phase with examples and enforces TDD principles to prevent shortcuts.
by parcadei
You can rapidly process multiple subcontractor bid responses—from trade contractors, material suppliers, and specialty vendors—into a cohesive, auditable estimate structure. Claude extracts key bid components, identifies pricing inconsistencies against benchmarks or prior projects, flags scope gaps and exclusions, and organizes everything by CSI division for seamless estimate assembly. This eliminates manual spreadsheet comparison and reduces the risk of overlooked scope omissions or pricing anomalies when managing 15+ concurrent bids.
by parcadei
You can deploy this agent to execute specific implementation tasks within a larger development plan. It operates independently with fresh context, follows test-driven development principles for every code change, and creates comprehensive handoff documentation that captures progress, decisions, and learnings for the next task executor. This ensures consistent code quality, prevents rework, and maintains continuity across distributed implementation efforts.
by parcadei
You can create reusable slash commands that execute instantly in Claude Code conversations. Commands support bash execution, file references, arguments, and tool permissions. Use built-in commands like /cost, /review, /memory, and /clear, or define custom project and personal commands stored in .claude/commands/ or ~/.claude/commands/.
by parcadei
Solve algebraic and transcendental equations, compute derivatives and integrals, perform matrix operations, simplify expressions, compute limits and series expansions, solve differential equations, and convert units. Claude automatically selects the best computational engine for your problem—SymPy for symbolic math, Z3 for logical proofs, Pint for unit conversion—so you get fast, verified answers without manual tool selection.
by parcadei
You can systematically analyze construction estimates by breaking down components, validating labor and material pricing against market data, identifying embedded errors or outdated assumptions, and applying data-driven contingency allocation. Claude helps you produce risk-adjusted cost projections that are defensible to stakeholders and competitive in bid scenarios, reducing estimate variance and catching pricing gaps before client submission.
by parcadei