Loading...
Loading...
Found 3,742 Skills
Merge validated feature to main via PR, tag release, cleanup worktree. Use after /feature-validate passes. Use for "release feature", "merge feature", "ship it", or "/feature-release". Do NOT use without passing validation or for hotfixes that skip the pipeline.
UPDATE-DOCS phase. Refresh README.md, CLAUDE.md, and docs/index.html to reflect changes made this session. Commits and pushes doc updates. Terminal phase — declares COMPLETE.
End-to-end workflow—review changes, create a Japanese commit per commit-jp, run pnpm lint && pnpm test, then push to origin per push. Use when the user wants to commit and publish in one go. Does not open or update PRs—use create-pr-jp for that.
Select an installation method, install NocoBase, and start it locally or on a server. Use when users ask how to install NocoBase, initialize a project, or start a running instance.
Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.
When the user wants help with Google Ads bidding strategies, Smart Bidding (Target CPA, Target ROAS, Maximize Conversions, Maximize Conversion Value), manual CPC, bid adjustments, portfolio bid strategies, bid modifiers, or optimizing bids across campaigns. Triggers on 'bidding strategy', 'Smart Bidding', 'Target CPA', 'Target ROAS', 'maximize conversions', 'manual CPC', 'bid adjustment', 'bid modifier', 'portfolio strategy', 'automated bidding', 'tROAS', 'tCPA', or 'bid too high/low'. For conversion data required for Smart Bidding see google-ads-conversion-tracking.
Adopt the Three Provinces and Six Ministries style code review, output structured review conclusions in five stages: Zhongshu Sheng, Shangshu Sheng, Six Ministries, Menxia Sheng, and Jinyiwei
Archive completed milestone and prepare for next version
Use when encountering bugs, test failures, or error logs that need root cause analysis and fix generation
Automated code review and analysis. Use when: user wants to review code changes, check for issues, analyze complexity, or perform security scans.
This skill should be used when a user wants to decompose an Epic into its complete set of Features all at once, invoked automatically after write-epic completes, or triggered by phrases like "create all features for this epic", "walk me through all the features", "let's break down this epic", or "plan the features for epic
This skill should be used when a developer or QA engineer wants to report a bug, create a bug ticket, document a test failure, log a defect, file an issue found during a QA session, or report something that is broken — for example "report a bug", "create a bug ticket", "I found a defect", "something is broken in task