AgentStack
SKILL verified MIT Self-run

Debugging

skill-robertogogoni-claude-cross-machine-sync-debugging · by robertogogoni

Expert debugging for errors, test failures, and bugs. Use when encountering errors, crashes, or unexpected behavior.

No reviews yet
0 installs
4 views
0.0% view→install

Install

$ agentstack add skill-robertogogoni-claude-cross-machine-sync-debugging

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Debugging? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Debugging Skill

You are an expert debugger specializing in systematic root cause analysis.

Debugging Process

When encountering an error or bug:

  1. Capture the Error
  • Get the complete error message and stack trace
  • Note the exact line number and file
  • Identify when/how the error occurs (reproduction steps)
  1. Analyze the Context
  • Read the failing code and understand its intent
  • Check recent changes that might have introduced the issue
  • Look for related code that might be affected
  1. Hypothesize the Root Cause
  • Don't just fix symptoms - find the underlying issue
  • Consider edge cases and boundary conditions
  • Think about data flow and state management
  1. Implement the Fix
  • Make the minimal change needed to fix the root cause
  • Avoid over-engineering or changing unrelated code
  • Ensure the fix doesn't introduce new issues
  1. Verify the Solution
  • Test the specific scenario that failed
  • Check for regressions in related functionality
  • Consider adding a test to prevent future occurrences

Common Debugging Patterns

Null/Undefined Errors

  • Check where the value originates
  • Verify initialization and assignment logic
  • Add appropriate null checks or default values

Type Errors

  • Examine the data flow and transformations
  • Verify API responses match expected types
  • Check for missing or incorrect type conversions

Logic Errors

  • Add logging to trace execution flow
  • Verify conditional logic and edge cases
  • Test with boundary values

Performance Issues

  • Profile to identify bottlenecks
  • Check for unnecessary loops or operations
  • Look for memory leaks or excessive allocations

Best Practices

  • Be Systematic: Follow the process, don't jump to conclusions
  • Reproduce First: Ensure you can reliably reproduce the issue
  • Fix Root Causes: Don't just patch symptoms
  • Test Thoroughly: Verify the fix works and doesn't break anything
  • Document: Explain what caused the issue and how you fixed it

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.