Debug mode workflows and best practices for troubleshooting bugs, regressions, and performance issues. Use when debugging tricky issues that standard agent interactions struggle with.
Scanned 2/12/2026
Install via CLI
openskills install NeverSight/skills_feed---
name: debug-mode
description: "Debug mode workflows and best practices for troubleshooting bugs, regressions, and performance issues. Use when debugging tricky issues that standard agent interactions struggle with."
---
# Debug Mode Skill
Specialized workflows for Debug Mode: hypothesis generation, log instrumentation, runtime analysis, and targeted fixes.
## When to Use
Use this skill when:
- Debugging tricky bugs that are hard to reproduce
- Investigating regressions
- Analyzing performance issues
- Troubleshooting race conditions
- Standard agent interactions aren't working
## Debug Mode Workflow
### 1. Exploration and Hypothesis
**Agent will:**
- Explore relevant code paths
- Generate hypotheses about root causes
- Identify potential failure points
- Plan instrumentation strategy
### 2. Instrumentation
**Agent adds:**
- Log statements at key points
- State tracking (variables, buffers, connections)
- Timing information
- Error condition checks
### 3. Reproduction
**You provide:**
- Detailed reproduction steps
- Expected vs actual behavior
- Error messages and stack traces
- Context about when bug occurs
### 4. Analysis
**Agent analyzes:**
- Collected logs
- State transitions
- Timing patterns
- Error conditions
### 5. Fix
**Agent makes:**
- Targeted fix based on evidence
- Minimal changes to address root cause
- Verification of fix
- Cleanup of instrumentation
## Best Practices
1. **Provide detailed context**: More information = better hypotheses
2. **Reproduce consistently**: Follow steps exactly
3. **Multiple reproductions**: For intermittent bugs
4. **Review fixes**: Ensure root cause addressed
5. **Clean up**: Remove instrumentation after fix
## Related Resources
- Rule: `.cursor/rules/agent-modes.mdc`
- Command: `/debug`
- Agent: `.cursor/skills/debug-mode/agents/debug-specialist.md`
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...