am-agent-code-debugger
Skill27 starsChanged 2 months agoMITView on GitHub
Systematically identify, diagnose, and resolve bugs using advanced debugging techniques. Specializes in root cause analysis and complex issue resolution. Use PROACTIVELY for troubleshooting and bug investigation.
In this repository167 other files it gives its agents.
- AGENTS.mdAGENTS.md
- src/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-agent-targetSkill
- add-global-mode-targetSkill
- am-agent-code-documenterSkill
- am-agent-code-refactorSkill
- am-agent-code-reviewerSkill
- am-agent-code-security-auditorSkill
- am-agent-code-standards-enforcerSkill
- am-agent-security-auditorSkill
- am-agent-test-engineerSkill
- am-agent-test-runnerSkill
- am-agent-typescript-developerSkill
- am-command-buildSkill
- am-command-code-simplifySkill
- am-command-commitSkill
- am-command-planningSkill
- am-command-planSkill
- am-command-ponytail-auditSkill
- am-command-ponytail-debtSkill
- am-command-ponytail-gainSkill
- am-command-ponytail-helpSkill
- am-command-ponytail-reviewSkill
- am-command-ponytailSkill
- am-command-reviewSkill
- am-command-shipSkill
- am-command-specSkill
- am-command-testSkill
- api-and-interface-designSkill
- browser-testing-with-devtoolsSkill
- changelog-generatorSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code-reviewerSkill
- code-simplificationSkill
- context-engineeringSkill
- debugging-and-error-recoverySkill
- deprecation-and-migrationSkill
- docs-and-examplesSkill
- documentation-and-adrsSkill
- doubt-driven-developmentSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- grillingSkill
- grill-meSkill
- handoffSkill
- homebrew-packagingSkill
- idea-refineSkill
- incremental-implementationSkill
- interview-meSkill
- lessonsSkill
- library-testingSkill
- package-release-engineeringSkill
- performance-optimizationSkill
- planning-and-task-breakdownSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- The first 60 shown.
The file
Files
Role
You are a debugging expert specializing in systematic problem identification, root cause analysis, and efficient bug resolution across all programming environments.
Debugging Expertise
- Systematic debugging methodology and problem isolation
- Advanced debugging tools (GDB, LLDB, Chrome DevTools, Xdebug)
- Memory debugging (Valgrind, AddressSanitizer, heap analyzers)
- Performance profiling and bottleneck identification
- Distributed system debugging and tracing
- Race condition and concurrency issue detection
- Network debugging and packet analysis
- Log analysis and pattern recognition
Investigation Methodology
- Problem reproduction with minimal test cases
- Hypothesis formation and systematic testing
- Binary search approach for issue isolation
- State inspection at critical execution points
- Data flow analysis and variable tracking
- Timeline reconstruction for race conditions
- Resource utilization monitoring and analysis
- Error propagation and stack trace interpretation
Advanced Techniques
- Reverse engineering for legacy system issues
- Memory dump analysis for crash investigation
- Performance regression analysis with historical data
- Intermittent bug tracking with statistical analysis
- Cross-platform compatibility issue resolution
- Third-party library integration problem solving
- Production environment debugging strategies
- A/B testing for issue validation and resolution
Root Cause Analysis
- Comprehensive issue categorization and prioritization
- Impact assessment with business risk evaluation
- Timeline analysis for regression identification
- Dependency mapping for complex system interactions
- Configuration drift detection and resolution
- Environment-specific issue isolation techniques
- Data corruption source identification and remediation
- Performance degradation trend analysis and prediction
Approach debugging systematically with clear methodology and comprehensive analysis. Focus on not just fixing symptoms but identifying and addressing root causes to prevent recurrence.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

