- Home
- /
- Categories
- /
- Debugging
Debugging
Find and fix bugs, error analysis
project-workflow
by zhucl1006
文档驱动的项目开发工作流。智能判断任务类型,执行已有计划或使用 project-planning 生成新计划。 使用场景: - 已有完整项目文档,需要执行开发任务 - 用户指定执行某个计划(如"执行 plan 001") - 用户请求开发新功能(使用 project-planning 生成计划) 前置条件: - 项目应该已有 docs/ 文档结构(PRD、SAD 等) - 如果是新项目,建议先使用 project-docs-setup skill 创建完整文档 - 如果需要制定计划,建议使用 project-planning skill 与其他 skill 的关系: - project-docs-setup:创建项目文档结构 - project-planning:制定开发计划(需求澄清 + 设计讨论 + 计划编写) - project-workflow:执行开发计划 + 更新文档 - 建议流程:project-docs-setup → project-planning → project-workflow 触发方式: - "执行 plan 001" / "继续 001-user-authentication" - "开始开发" / "执行计划" / "继续上次的任务"
git-commit-plan
by heykvnzhao
Plan commits from the current working tree. Use when asked how to split changes into commits, what to stage together, how to handle untracked files, or to propose commit messages and an execution plan (stage/commit) based on git status/diffs.
coding-standards
by automindtechnologie-jpg
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
opencode-crane
by AugustChaoTW
CRANE — Autonomous research assistant MCP server with 124 tools covering the full academic research lifecycle. Key trigger phrases: "paper trace" / "do paper trace" → trace_paper; "evaluate paper" / "score paper" → evaluate_paper_v2; "review paper" / "detect defects" → crane_review_full; "diagnose paper" / "diagnose section" → crane_diagnose; "submission check" / "投稿前檢查" → run_submission_check; "simulate submission" / "acceptance probability" → simulate_submission_outcome; "review pipeline" / "full review" → run_review_pipeline; "build index" / "scan paper" → build_paper_index; "semantic search" / "find similar" → semantic_search; "ask library" / "rag" → ask_library; "match journal" → match_journal_v2; "citation graph" → visualize_citations; "karpathy review" / "code review" → karpathy_review; "literature review" / "search papers" → run_pipeline(pipeline="literature-review"); "init project" / "setup" → run_pipeline(pipeline="full-setup"); "what can crane do" / "help" → crane_help(topic=...) or list_workflows().
frontend-patterns
by hubeiqiao
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
auto-doc
by Xunzi229
自动根据 git diff 或代码变更更新 README.md 和 CHANGELOG.md。
debugging-strategies
by TriNgo0108
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
Development Workflow — BreakPerfect Gaming Lounge Management App
by vippinn-ai
See architect.md for how the system is built and why it is designed the way it is.
handle-pr-feedback
by squirrel289
"Coordinate PR review loop—detect feedback severity, address minor comments automatically, revert work items if major changes needed. Use when PR has unresolved review feedback. Supports: (1) Comment triage by severity, (2) Auto-resolution of minor comments, (3) Work item reversion on blocker feedback, (4) Feedback summarization"
gsDesignNB
by keaven
Design, simulate, and adapt clinical trials with negative binomial recurrent event endpoints using the gsDesignNB R package. Use this skill when the task involves: NB sample size or power, event gaps and Jensen correction, calendar-time group sequential design, blinded or unblinded information estimation, sample size re-estimation (SSR), recurrent-event simulation (constant or seasonal rates), interim data cuts, completer-based analyses, or non-inferiority/super-superiority designs for recurrent events.
preventing-error-exposure
by djankies
Prevent leaking database errors and P-codes to clients. Use when implementing API error handling or user-facing error messages.
devdocs-dev-workflow
by ab300819
Execute development tasks with skeleton-first approach and layered TDD. Supports single task, batch execution (by range, feature, user story), dependency resolution, and breakpoint resume. Includes optional adversarial verification and --headless unattended mode (无人值守). Triggers on "execute task", "start T-XX", "batch", "resume", "开发任务", "执行任务", "批量开发", "继续开发", "--review", "--headless", "无人值守".
cli-developer
by Olino3
Forge is a marketplace for a Claude Code Plugins
rust-hexagonal-architecture
by oryjk
Complete implementation guide for Rust projects using Hexagonal Architecture with vertical slicing. Use when working with Rust/Axum/PostgreSQL projects that require clean architecture principles, domain-driven design, or when implementing new features following strict architectural patterns. Essential for maintaining code quality and architectural consistency in backend projects.
commit
by hrdtbs
Enforces Conventional Commits format when creating git commits. Use this skill whenever you need to create a commit message. Triggers on "commit", "git commit", "コミット", "変更をコミット".
dotnet-recommended
by idotta
Use when building .NET 10 or C# 14 applications; when using minimal APIs, modular monolith patterns, or feature folders; when implementing HTTP resilience, Options pattern, Channels, or validation; when seeing outdated patterns like old extension method syntax
mcp-detector
by zwmmm
Automatically detect and suggest appropriate MCP tools (context7, grep_app, web_search) based on user queries. Use when queries contain documentation keywords (how to use, docs, API, guide, tutorial, 如何使用, 文档, 教程); code search keywords (example, implementation, source code, github, 例子, 示例, 实现, 源码); or latest information/bug fixing keywords (latest, 2025, 2026, new, update, fix bug, error, 最新, 更新, 修复 bug, 报错).
notifications-feedback
by moderndegree
Toast notifications, alerts, feedback messages, and their timing. Use when adding user feedback, success messages, or alerts.
competing-hypotheses
by shhac
Debug problems by investigating multiple hypotheses in parallel. Use when you have a bug, unexpected behaviour, or mystery where the root cause is unclear. Spawns parallel investigator agents each pursuing a different theory, then compares evidence to identify the most likely cause and fix.
flutter-dev
by bogdanustyak
Expert Flutter and Dart development skill for building beautiful, performant, and maintainable applications. Use when users request Flutter/Dart development tasks including creating apps, widgets, screens, implementing features, debugging, testing, state management, navigation, theming, layouts, or working with Flutter projects. Covers mobile, web, and desktop platforms with modern best practices, Material Design, responsive UI, and code quality standards.
Performance Optimizer
by anorbert-cmyk
Web Performance Optimizer (frontend + backend aware) converting performance findings into code-level fixes.
debug-dataflow
by ShotaIuchi
Data flow tracing investigation. Apply when debugging data transformation errors, boundary conditions, type conversions, null propagation, and unexpected data mutations.
systematic-debugging
by vilin1927
Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.
vue-best-practices
by yuanxiao0115
Vue 3 TypeScript, vue-tsc, Volar, Vite, component props, testing, composition API.