调试
定位并修复问题，分析错误
analyze-ci-logs
dykyi-roman
Analyzes CI/CD pipeline logs to identify failure causes. Parses error messages, detects common failure patterns, and provides fix recommendations.
analyze-docker-build-errors
dykyi-roman
Analyzes Docker build errors for PHP projects. Identifies extension compilation failures, dependency issues, memory limits, and provides fixes.
bug-root-cause-finder
dykyi-roman
Root cause analysis methods for PHP bugs. Provides 5 Whys technique, fault tree analysis, git bisect guidance, and stack trace parsing.
bug-impact-analyzer
dykyi-roman
Analyzes bug fix blast radius. Determines affected code, dependencies, callers/callees, and potential side effects of changes.
Debugging - Systematic Code Investigation
DNYoussef
Context Cascade - Nested Plugin Architecture for Claude Code Official Claude Code Plugin Version 3.1.0 Last updated: 2026-01-09 (see docs/COMPONENT-COUNTS.json for source counts) Context-saving nested architecture: Playbooks -> Skills -> Agents -> Commands. Load only what you need, saving 90%+ context space.
Debugging Assistant Skill
DNYoussef
Context Cascade - Nested Plugin Architecture for Claude Code Official Claude Code Plugin Version 3.1.0 Last updated: 2026-01-09 (see docs/COMPONENT-COUNTS.json for source counts) Context-saving nested architecture: Playbooks -> Skills -> Agents -> Commands. Load only what you need, saving 90%+ context space.
signoz-observability
LightHeart-Ventures
Agent-driven half of the SigNoz Observability plugin. Use when a repo has just been detected/opened and you want an OpenTelemetry instrumentation profile, or after a turn to check SigNoz for fresh exceptions in the active repo's services. Triggers on: "scan this repo for instrumentation", "any new exceptions?", "check signoz", "what services does this repo emit", "observability status". Pairs with the fork/exec scripts in bin/ (which handle the MCP-free REST path); THIS file is what YOU (the agent) follow when the signoz MCP tools are available.
Smart Bug Fix
DNYoussef
Context Cascade - Nested Plugin Architecture for Claude Code Official Claude Code Plugin Version 3.1.0 Last updated: 2026-01-09 (see docs/COMPONENT-COUNTS.json for source counts) Context-saving nested architecture: Playbooks -> Skills -> Agents -> Commands. Load only what you need, saving 90%+ context space.
hermes-mcp-tool-config
HMS091
Configure MCP servers and third-party tools for Hermes on Windows — install, register, troubleshoot, and verify external tool connections. Covers cua-driver, browser automation, and any stdio-based MCP server.
executive-onboarding-playbook
HMS091
Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.
fp-types-ref
whatiskadudoing
Quick reference for fp-ts types. Use when user asks which type to use, needs Option/Either/Task decision help, or wants fp-ts imports.
vp-cpo-readiness-advisor
HMS091
Guide the transition to VP or CPO across preparing, interviewing, landing, and recalibrating. Use when executive product scope is changing fast.
bug-blitz
ArjenSchwarz
Batch-fix all open bugs in parallel using git worktrees. Fetches bug-type tasks in "idea" status from Transit, creates an isolated worktree per bug, and spawns parallel subagents each running the fix-bug workflow. Use when you want to tackle all open bugs at once, e.g. "fix all open bugs", "bug blitz", "resolve all Transit bugs".
systematic-debugging
dshakes
Use when something is broken — a failing test, panic, stack trace, error log, or wrong behavior whose cause isn't obvious. Reproduce it, form a hypothesis, PROVE the cause before changing code, then make the minimal root-cause fix and guard it with a test. For deep cases, hand off to the debugger subagent.
transit
ArjenSchwarz
Route Transit tickets to the appropriate workflow based on task type. Use when a user mentions a T-[number] ticket reference and wants to work on it. Fetches task details and dispatches to the correct skill (fix-bug, creating-spec, planning mode, or asks for clarification).
fix-bug
ArjenSchwarz
Systematic bug investigation, resolution, and documentation. Use when fixing bugs that need thorough analysis, test coverage, and a formal bugfix report. Applies systematic debugging methodology, creates regression tests, and generates a standardized report in specs/bugfixes/<bug-name>/. Triggers on requests like "fix this bug", "debug and document this issue", or when a bug needs both resolution and documentation.
performing-systematic-debugging-for-stubborn-problems
ArjenSchwarz
Applies a modified Fagan Inspection methodology to systematically resolve persistent bugs and complex issues. Use when multiple previous fix attempts have failed repeatedly, when dealing with intricate system interactions, or when a methodical root cause analysis is needed. Do not use for simple troubleshooting. Triggers after multiple failed debugging attempts on the same complex issue.
🔧 Error Handling Skill
wasintoh
Last Updated: 2024-12-03
backend-engineer
wasintoh
Supabase integration specialist. Handles database schema, authentication, Row Level Security (RLS), real-time subscriptions, and storage. Connects existing UI to real backend. Only called AFTER UI exists with mock data. Triggers: connect database, connect Supabase, add auth, make login, backend integration, real data, authentication, database schema.
dev-engineer
wasintoh
Adds logic, state management, TypeScript types, and CRUD operations to UI. Works AFTER ui-first-builder creates the interface. Implements Zustand stores, form handling with React Hook Form + Zod, and prepares for backend connection. Triggers: add logic, add functionality, make it work, state management, form validation, data operations, TypeScript types.
ccxt
2025Emma
CCXT cryptocurrency trading library. Use for cryptocurrency exchange APIs, trading, market data, order management, and crypto trading automation across 150+ exchanges. Supports JavaScript/Python/PHP.
failure-taxonomy
maragudk
Build a structured taxonomy of failure modes from open-coded trace annotations. Use this skill whenever the user has freeform annotations from reviewing LLM traces and wants to cluster them into a coherent, non-overlapping set of binary failure categories (axial coding). Also use when the user mentions "failure modes", "error taxonomy", "axial coding", "cluster annotations", "categorize errors", "failure analysis", or wants to go from raw observation notes to structured evaluation criteria. This skill covers the full pipeline: grouping open codes, defining failure modes, re-labeling traces, and quantifying error rates.
API Design Skill
nth5693
```
skipped-test-manager
klamping
Use when temporarily skipping failing WebdriverIO tests for app bugs or unimplemented functionality, while tracking ownership, ticket linkage, and re-enable status.