调试
定位并修复问题，分析错误
git-advanced-workflows
julianobarbosa
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
csharp
LdotJdot
用于在 C# / .NET 项目中进行规划、实现、重构和调试。优先使用 dotnet CLI 完成项目管理与编译，结合 Grep / SemanticSearch / 子代理 / 网络搜索进行代码定位与 Debug。禁止执行 dotnet run / dotnet test，编译通过即视为任务完成。
code-flow-tracer
lis186
Trace code execution paths and data flow. Use when user asks "how does X work", "what happens when X", "trace the flow of X", "where does data come from", or needs to understand feature implementation.
python-best-practices
jkitchin
Expert guidance for writing professional Python code following industry best practices including PEP 8 compliance, testing, type hints, error handling, and modern tooling. Use this skill when writing new Python code, refactoring existing code, setting up Python projects, implementing tests, or ensuring code quality and maintainability. Emphasizes: PEP 8, modularity, DRY principle, TDD, virtual environments (uv), and modern tooling (Ruff, Black, Mypy).
code-reviewer
jkitchin
Comprehensive code review and analysis for software quality assurance. Use when Claude needs to review code in any format including (1) Individual files (Python, R, JavaScript, etc.), (2) Directory structures and project organization, (3) Scripts and automation code, (4) Jupyter notebooks and data analysis workflows, (5) Documentation assessment and improvement suggestions, (6) Bug detection and logic verification, (7) Testing coverage and strategy evaluation, (8) Code consistency and maintainability analysis. Provides actionable improvement recommendations across all aspects of software development.
flow
lis186
Extract business logic flow from code, trace execution path from entry point
local-issue
DoiiarX
"本地文件系统 issue 管理。Use when the user wants to create, update, or close a local issue, report a bug, add a feature request, or track a task in the local file-based issue system. Triggers on: local issue, 本地issue, 创建issue, 新建issue, bug report, feature request, 关闭issue, 创建任务."
home-assistant-automation-scripts
bradsjm
Home Assistant automations, scripts, and blueprints. Use when the user requests automation/script syntax, triggers/conditions/actions, blueprint usage, run modes, or troubleshooting, and when mapping those needs to ha-mcp automation/script tools.
testing-dags
necatiarslan
Complex DAG testing workflows with debugging and fixing cycles. Use for multi-step testing requests like "test this dag and fix it if it fails", "test and debug", "run the pipeline and troubleshoot issues".
debugging-dags
necatiarslan
Comprehensive DAG failure diagnosis and root cause analysis. Use for complex debugging requests requiring deep investigation like "diagnose and fix the pipeline" or "full root cause analysis".
tracing-downstream-lineage
necatiarslan
Trace downstream data lineage and impact analysis. Use when the user asks what depends on this data, what breaks if something changes, downstream dependencies, or needs to assess change risk before modifying a table or DAG.
tracing-upstream-lineage
necatiarslan
Trace upstream data lineage. Use when the user asks where data comes from, what feeds a table, upstream dependencies, data sources, or needs to understand data origins.
correcting-mistakes
Sawyer-Middeleer
Self-corrects skill and command instructions after resolving errors. Use when Claude errors during skill/command execution and finds a solution, or when user indicates a mistake was made. Finds the relevant instruction file and applies succinct fixes.
ast-grep-setup
alchemiststudiosDOTai
Set up ast-grep for a codebase with common TypeScript rules for detecting anti-patterns, enforcing best practices, and preventing bugs. Creates sgconfig.yml, rule files, and rule tests. Use when adding structural linting, banning legacy patterns, or implementing ratchet gates.
clean-tests
ertugrul-dmr
Use when writing, fixing, editing, or refactoring Python tests. Enforces Clean Code principles—fast tests, boundary coverage, one assert per test.
technical-writer
olehsvyrydov
Senior Technical Writer with 10+ years documenting complex systems. Use when creating/updating documentation, writing API docs, creating architecture diagrams (C4, Mermaid), generating changelogs, writing READMEs, or creating onboarding guides.
tester
olehsvyrydov
Rob - Senior QA Engineer specializing in black-box testing and feature validation. Use when testing features against acceptance criteria, validating user requirements, creating test reports, or performing exploratory testing. Also responds to 'Rob' or /rob command.
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.
framework-initiative
rfxlamia
Framework for agents to understand implicit user intent, think before acting, and consider action impact. Uses STAR framework (Stop-Think-Analyze-Respond) to prevent literal execution that doesn't match context. Use when agent receives ambiguous requests, abstract commands like "fix", "improve", "delete all", or actions with potential wide-scope impact. Trigger on code modification requests without explicit scope constraints.
gitnexus-debugging
docxology
"Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\""
nix
i9wa4
Nix commands and package management guide. Use when: - Running nix build, nix run - Adding custom packages - Using nurl for hash acquisition
laravel-iterating-on-code
noartem
Refine AI-generated code through specific feedback—point out errors, identify gaps, show desired changes, reference style guides
claude-workspace-trust-fix
i9wa4
Fix for Claude Code PreToolUse hooks being silently skipped in interactive mode. Sets hasTrustDialogAccepted: true for all project entries in ~/.claude/.claude.json. Use when: - PreToolUse hooks are not firing in interactive mode - Hooks work in -p mode but not interactive - User says "fix workspace trust" or "hooks not working" - Setting up Claude Code on a new machine - After adding new projects to Claude Code