Agent skill

debugging

Root cause analysis and debugging protocols. Use when encountering errors, test failures, unexpected behavior, stack traces, or when code behaves differently than expected.

Stars 8
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/siviter-xyz/dot-agent/tree/main/skills/debugging

SKILL.md

Debugging

Systematic approach to root cause analysis and debugging.

When to Use

  • Encountering errors or exceptions
  • Test failures that need investigation
  • Unexpected behavior in code
  • Stack traces or error messages
  • Code behaving differently than expected
  • Performance issues or bugs

Core Principles

  • Evidence-based: Base diagnosis on error messages, logs, and reproducible steps
  • Systematic: Follow structured debugging process
  • Minimal fixes: Implement smallest change that resolves issue
  • Verify solutions: Confirm fix works and doesn't introduce regressions

Debugging Process

Follow systematic debugging process:

  1. Capture error information (message, stack trace, logs, environment)
  2. Identify reproduction steps (minimal steps, conditions, edge cases)
  3. Isolate failure location (function/module, recent changes, dependencies)
  4. Form and test hypotheses (evidence-based, systematic testing, debug logging)
  5. Implement minimal fix (smallest change, preserve behavior, follow patterns)
  6. Verify solution (issue resolved, no regressions, tests pass)

See references/root-cause-analysis.md for detailed methods.

Strategic Debug Logging

Add debug logging to entry/exit points, state transitions, conditional branches, external API calls, and data transformations. Remove after issue resolved unless it provides ongoing value.

Error Pattern Recognition

Common patterns: null/undefined errors, type errors, timing issues, state corruption, configuration issues. See references/error-patterns.md for detailed patterns and solutions.

Integration

After fixing:

  • Verify CI passes (types, tests, lint)
  • Stage atomic changes (fix + tests)
  • Suggest semantic commit message
  • Confirm with user before committing

References

For detailed guidance, see:

  • references/root-cause-analysis.md - Systematic analysis methods
  • references/error-patterns.md - Common error patterns and solutions
  • references/debugging-tools.md - Debugging tools and techniques

Expand your agent's capabilities with these related and highly-rated skills.

siviter-xyz/dot-agent

frontend-engineer

Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.

8 0
Explore
siviter-xyz/dot-agent

code-review

Code review practices emphasizing technical rigor, evidence-based claims, and verification. Use when receiving code review feedback, completing tasks requiring review, or before making completion claims.

8 0
Explore
siviter-xyz/dot-agent

cursor-best-practices

Best practices for working with Cursor. Use when learning how to effectively use Cursor features or optimizing your workflow.

8 0
Explore
siviter-xyz/dot-agent

create-skill

Guide for creating effective skills following best practices. Use when creating or updating skills that extend agent capabilities.

8 0
Explore
siviter-xyz/dot-agent

semantic-git

Manage Git commits using conventional commit format with atomic staging. Always generate plain git commands before running them and offer to let the user run them manually.

8 0
Explore
siviter-xyz/dot-agent

backend-engineer

Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

8 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results