``` 1. Reproduce → Can you reliably trigger the bug? 2. Isolate → Find the minimal failing case 3. Analyze → Check logs, traces, metrics 4. Hypothesize → Form a theory 5. Test → Verify the theory 6. Fix → Implement the solution 7. Verify → Ensure fix works 8. Prevent → Add test/monitoring ``` ```typescript // Add request ID app.use(async (req, res, next) => { req.id = req.headers['x-request-id
Scanned 9/7/2026
Install to Claude Code
npx -y skills add modbender/skill-library-mcp --skill debugging --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Debugging?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/modbender-debugging)More formats (shields.io, HTML) on the badges page.
# Debugging Across Platforms
## Debugging Workflow
```
1. Reproduce → Can you reliably trigger the bug?
2. Isolate → Find the minimal failing case
3. Analyze → Check logs, traces, metrics
4. Hypothesize → Form a theory
5. Test → Verify the theory
6. Fix → Implement the solution
7. Verify → Ensure fix works
8. Prevent → Add test/monitoring
```
## Request Tracing
```typescript
// Add request ID
app.use(async (req, res, next) => {
req.id = req.headers['x-request-id'] ?? crypto.randomUUID()
res.setHeader('x-request-id', req.id)
next()
})
// Log with request ID
app.use((req, res, next) => {
const start = Date.now()
res.on('finish', () => {
logger.info({
requestId: req.id,
method: req.method,
path: req.path,
status: res.statusCode,
duration: Date.now() - start,
})
})
next()
})
```
## Production Debugging Safety
- [ ] Never use production data in tests
- [ ] Add verbose logging temporarily
- [ ] Use read-only database connections
- [ ] Limit data exposure in logs
- [ ] Roll back changes after debugging
## Checklist
- [ ] Add request IDs
- [ ] Set up centralized logging
- [ ] Use debugging tools (Chrome DevTools, curl)
- [ ] Check network tab
- [ ] Review server logs
- [ ] Use breakpoints (local dev only)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.