- Home
- /
- Categories
- /
- Debugging
Debugging
Find and fix bugs, error analysis
code-review-python
by Jamie-BitFlight
Provides Python-specific code review rules for the dh code-reviewer agent. Activates on pyproject.toml or *.py file detection — enforces uv, ruff, ty, pytest, type annotation, error handling, and Python 3.11+ idioms including pathlib, match statements, and modern union syntax.
perl-development
by Jamie-BitFlight
This skill should be used when the user asks to "write a Perl script", "create Perl code", "modern Perl best practices", "Perl 5.30+", "use strict warnings autodie", or mentions Perl pragmas, subroutines, error handling, or scripting patterns. Provides comprehensive Perl 5.30+ development guidance.
group-items-to-milestone
by Jamie-BitFlight
'Assign backlog items to a GitHub milestone by bridging per-item files to GitHub Issues. Use when populating a sprint or release milestone, after create-milestone, or when a milestone number is specified with optional P0/P1/P2 or title filter. Creates missing GitHub Issues for selected P0/P1 items, assigns all selected items to the milestone, and updates Project V2 Status to Backlog.'
holistic-linting-resolver
by Jamie-BitFlight
Linter-specific resolution workflows for ruff, mypy, pyright, and basedpyright. Provides systematic root-cause analysis procedures, suppression gates, and verification steps. Use when resolving linting errors as a sub-agent, implementing fixes systematically, or conducting type flow analysis.
analyze-test-failures
by Jamie-BitFlight
Use when analyzing failing test cases to determine whether failures indicate genuine bugs or test implementation issues. Activates on "analyze failing tests", "debug test failures", "investigate test errors", or when provided with specific failing test names or output. Applies balanced investigative reasoning — does not auto-fix tests without establishing root cause.
validation-protocol
by Jamie-BitFlight
Scientific validation protocol for verifying fixes work through observation, not assumption. Use when claiming a bug fix, code change, or implementation is complete. Enforces create-broken-state — define-success-criteria — apply-fix — verify-outcome workflow. Success equals observing intended behavior, not absence of errors.
C++ 开发技能指南
by wanghenshui
asteria — 可嵌入脚本语言
logql-generator
by akin-ozer
Comprehensive toolkit for generating best practice LogQL (Loki Query Language) queries following current standards and conventions. Use this skill when creating new LogQL queries, implementing log analysis dashboards, alerting rules, or troubleshooting with Loki.
software-developer
by nahisaho
software-developer skill Trigger terms: implement, code, development, programming, coding, build feature, create function, write code, SOLID principles, clean code, refactor Use when: User requests involve software developer tasks.
business-model-auditor
by shipshitdev
Use this skill when users need to stress test their business model, identify scale limitations, find bottlenecks, determine if they're trading time for money, or evaluate unit economics. Activates for "can this scale," "what breaks at 10x," or business model viability questions.
diagnose
by mycelium-hq
'Use when an AI Brain vault needs a health check or something feels off: Claude ignores CLAUDE.md, journal entries missing from /weekly, hooks not firing, something broke after a git pull, a friend''s install misbehaves, Obsidian crashes or pegs the CPU, a .claude/worktrees folder appeared, Granola/WhatsApp/Slack/Gmail notes stopped arriving, or Windows .ps1 scripts error. Also after major /setup-brain upgrades. Not for debugging code; audits the vault install only.'
code-review
by iliaal
Performs two-stage code reviews (spec compliance, then code quality) with severity-ranked findings. Use when asked to "review code", "review this PR", "check this diff", "review before merge", or mentions reviewing, auditing, or critiquing code changes, pull requests, or diffs.
mpm-doctor
by bobmatnyc
Run diagnostic checks on Claude MPM installation
pm-bug-reporting
by bobmatnyc
Bug reporting protocol for PM and agents to file GitHub issues
Root Cause Tracing
by bobmatnyc
Systematically trace bugs backward through call stack to find original trigger
toolchains-golang-core
by bobmatnyc
"Go 1.22+ core patterns for minimalism, efficiency, code reuse, and performance"
Testing Anti-Patterns
by bobmatnyc
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
daemon-start
by terrylica
Start the asciinema chunker daemon. TRIGGERS - start daemon, resume chunker, enable backup.
ascii-diagram-validator
by terrylica
Validate ASCII diagram alignment in markdown. TRIGGERS - diagram alignment, ASCII art, box-drawing diagrams.
daemon-setup
by terrylica
Set up asciinema chunker daemon with interactive wizard. Guides through PAT creation, Keychain storage, Pushover setup, and.
setup
by terrylica
Check and install dependencies for asciinema-tools. TRIGGERS - setup, check deps, preflight.
daemon-logs
by terrylica
View asciinema chunker daemon logs. TRIGGERS - daemon logs, chunker logs, backup logs.
asciinema-analyzer
by terrylica
Semantic analysis of asciinema recordings. TRIGGERS - analyze cast, keyword extraction, find patterns in recordings.
daemon-stop
by terrylica
Stop the asciinema chunker daemon. TRIGGERS - stop daemon, pause chunker, disable backup.