调试
定位并修复问题，分析错误
fix-ci
ryoppippi
Diagnoses and fixes CI failures with the gh CLI. Use when GitHub Actions checks are red and the failing logs need to be fetched, analysed, and resolved.
react-server-components
ryoppippi
Reviews React Server/Client Component boundaries against Next.js and React docs. Use when auditing 'use client' placement or splitting components for proper RSC behaviour.
explore-plan
AlexanderMattTurner
Drives the Explore -> Plan -> Critique -> Review -> Verify discipline for a written plan. Activate on entry to plan mode, before writing the plan — including the plan-mode requests "plan this", "scope this out", "figure out how to do X", "explore the codebase first" — in auto mode at the start of any non-trivial task, where no plan gate fires — and in any other mode when the task obviously needs a plan (several files, an unfamiliar subsystem, more than one PR), invoked informally without entering plan mode. A trivial edit (typo, single-line change) activates nothing, in any mode. Enforces a self-critiqued written plan, convergent setup work started in the background while design questions settle, and real verification instead of trusting a success claim.
debugging
axiomantic
"Use when debugging bugs, test failures, or unexpected behavior. Triggers: 'why isn't this working', 'this doesn't work', 'X is broken', 'something's wrong', 'getting an error', 'exception in', 'stopped working', 'regression', 'crash', 'hang', 'flaky test', 'intermittent failure', or when user pastes a stack trace/error output. NOT for: test quality issues (use fixing-tests), adding new behavior (use implementing-features)."
async-await-patterns
axiomantic
"Use when writing JavaScript or TypeScript code with asynchronous operations, fixing promise-related bugs, or converting callback/promise patterns to async/await. Triggers: 'promise chain', 'unhandled rejection', 'race condition in JS', 'callback hell', 'Promise.all', 'sequential vs parallel async', 'missing await'. Enforces async/await discipline over raw promises."
brainstorming
axiomantic
"Use when exploring design approaches, generating ideas, or making architectural decisions. Triggers: 'explore options', 'what are the tradeoffs', 'how should I approach', 'let's think through', 'sketch out an approach', 'I need ideas for', 'how would you structure', 'what are my options'. Also used in SYNTHESIS mode when implementing-features provides discovery context for autonomous design."
fixing-tests
axiomantic
"Use when tests themselves are broken, test quality is poor, or user wants to fix/improve tests. Triggers: 'test is broken', 'test is wrong', 'test is flaky', 'make tests pass', 'tests need updating', 'green mirage', 'tests pass but shouldn't', 'audit report findings', 'run and fix tests'. Three modes: fix specific tests, process green-mirage audit findings, and run-then-fix. NOT for: bugs in production code caught by correct tests (use debugging)."
merging-worktrees
axiomantic
"Use when merging parallel worktrees back together after parallel implementation, combining parallel development tracks, or unifying branches from dispatched parallel agents. Triggers: 'merge worktrees', 'combine parallel branches', 'integrate parallel work', 'all tracks complete', 'bring everything together'."
test-driven-development
axiomantic
"Use when user explicitly requests test-driven development, says 'TDD', 'write tests first', 'red green refactor', 'test-first', or 'start with the test'. Also invoked as a sub-skill by implementing-features and executing-plans for each implementation task. NOT a replacement for implementing-features for full feature work."
auditing-green-mirage
axiomantic
"Use when auditing whether tests genuinely catch failures, or when user expresses doubt about test quality. Triggers: 'are these tests real', 'do tests catch bugs', 'tests pass but I don't trust them', 'test quality audit', 'green mirage', 'shallow tests', 'tests always pass suspiciously', 'would this test fail if code was broken'. Forensic analysis of assertions, mock usage, and code path coverage."
isolated-testing
axiomantic
Use when testing theories during debugging, or when chaos is detected. Triggers: "let me try", "maybe if I", "what about", "quick test", "see if", rapid context switching, multiple changes without isolation. Enforces one-theory-one-test discipline. Invoked automatically by debugging, scientific-debugging, systematic-debugging before any experiment execution.
fractal-thinking
axiomantic
Adaptive recursive thought engine for deep exploration. Invoked by other skills (brainstorming, fact-checking, debugging, deep-research) when they need to deeply explore uncertainty, systematically decompose complex questions, or gain certainty about multi-faceted problems. Triggers: "think deeply about", "explore this recursively", "I need certainty about", "decompose this question", "what am I missing". Also invoked programmatically with a seed, intensity, and checkpoint mode. NOT for: simple questions with known answers, linear task execution, or file-by-file code review.
code-review
akaszubski
"10-point code review checklist covering correctness, tests, error handling, type hints, naming, security, and performance. Use when reviewing PRs or evaluating code quality. TRIGGER when: code review, PR review, review checklist, code quality check. DO NOT TRIGGER when: writing new code, debugging, refactoring without review context."
macos-auto-update
fayazara
Add Sparkle auto-update support to a native macOS app. Use this skill whenever the user wants to add auto-updates, implement Sparkle, set up an appcast feed, add "Check for Updates" to their app, or integrate automatic update checking. Also trigger when the user mentions Sparkle, appcast, SUFeedURL, EdDSA signing, or update notifications. This covers the full setup: adding the Sparkle SPM dependency, creating the UpdaterManager singleton, wiring it into the app delegate and UI, configuring Info.plist, and generating the initial appcast.xml.
test-results-analyzer
aibangjuxin
You are a data-driven and insightful Test Results Analyzer. You are an expert at looking at the output of large, automated test suites, identifying patterns, and triaging failures. You help the engineering team quickly understand the health of a new build and prioritize which test failures to fix first.
committing-changes
gannonh
Use this skill when committing code changes, creating git commits, staging files for commit, or when the user asks to commit, save changes, or make a commit. Handles conventional commit format, explicit file staging, and commit message crafting.
cf-fix
dinhanhthi
Quick bug fix workflow. Use when the user reports a bug, error, or broken behavior — e.g. "fix this", "it's broken", "not working", "there's a bug", "I'm getting an error", "this crashes", "something is wrong", "why does this fail", "debug this", "it throws", "fix the issue", "resolve this error", "help me fix", "can you fix", "this doesn't work", "stopped working", "regression", "unexpected behavior", "failing test", "broken after update". Also triggers on stack traces, error messages, or descriptions of incorrect program behavior.
professional-development-superskill
robertpelloni
Comprehensive superskill consolidating 41 professional development skills across planning, testing, debugging, code review, git workflow, writing, architecture, meta-skills, thinking frameworks, and communication. Use when you need a complete reference for software development best practices, workflows, and methodologies.
cf-sys-debug
dinhanhthi
Use when diagnosing bugs, investigating failures, or fixing broken behavior
quarkus-panache-smells
emvnuel
Detects and refactors ORM code smells in Quarkus Panache applications using the Repository pattern. Use when reviewing PanacheRepository code, diagnosing N+1 queries, data overfetching, or pagination issues.
ruby-on-rails
display-design-studio
Comprehensive Ruby on Rails 8.1 best-practices skill covering MVC, Active Record, routing, views, background jobs, storage, security, testing, and performance. Use when the user mentions Rails, Ruby on Rails, ActiveRecord, ActiveJob, ActionMailer, ActionCable, Active Storage, rails generate, rails routes, Hotwire, Turbo, Stimulus, or asks to build, review, debug, or migrate a Rails application or API.
test-driven-development
yotamleo-org
Use when implementing any feature or bugfix, before writing implementation code
Homeware Sense - OpenClaw技能
malpaa44
最小化编码: 提供简化的快速接入接口
systematic-debugging
yotamleo-org
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes