check-stripe
0.00
|
3555 results
(26.6ms)
page 39 / 178
Use when receiving code review feedback, before implementing suggestions,
Assesses and responds to incoming code review feedback on PRs (reviewer comments, requested changes), especially when suggestions are unclear, technically questionable, or scope-expanding. Use...
citation-validator
0.00
验证研究报告中所有声明的引用准确性、来源质量和格式规范性。确保每个事实性声明都有可验证的来源，并提供来源质量评级。当最终确定研究报告、审查他人研究、发布或分享研究之前使用此技能。
Use when working with error diagnostics smart debug
Use when working with error diagnostics smart debug
Use when working with error diagnostics smart debug
Use when working with debugging toolkit smart debug
Use when working with debugging toolkit smart debug
Use when working with debugging toolkit smart debug
Use when working with error diagnostics smart debug
Use when working with debugging toolkit smart debug
sherlock-review
0.00
Evidence-based investigative code review using deductive reasoning to determine what actually happened versus what was claimed. Use when verifying implementation claims, investigating bugs,...
update-jamdesk
0.00
Use when user-facing code changes need documentation, user says "update docs"/"document this"/"add to jamdesk docs", or after implementing APIs, CLI commands, or UI components.
researchers-legal
0.00
Court documents, indictments, plea agreements, sentencing records
subagent-creator
0.00
Guide for creating AI subagents with isolated context for complex multi-step workflows. Use when users want to create a subagent, specialized agent, verifier, debugger, or orchestrator that...
prd
0.00
Create Product Requirements Documents (PRDs) through structured interviews. Use when the user asks to create a PRD, write requirements, spec out a feature, or needs help defining what to build.
mutate
0.00
Change persistent state with checkpoint and rollback support. Use when modifying files, updating databases, changing configuration, or any operation that permanently alters state.
inquire
0.00
Request clarification when input is ambiguous. Use when user request has missing parameters, conflicting interpretations, or insufficient constraints for reliable execution.
root-cause-analysis
0.00
Conducts systematic root cause analysis using proven methodologies including Toyota's 5 Whys, Ishikawa fishbone diagrams, Pareto analysis, and fault tree analysis. Use when investigating bugs,...