Loading...
Loading...
Found 2,378 Skills
This skill should be used when a user wants to plan and create the complete set of Tasks for a Feature all at once, systematically walk through every implementable slice of work for a Feature, or create tasks in batch with step-by-step confirmation. Triggers on phrases like "plan all tasks for this feature", "create all tasks for feature
Commit changes and create a pull request to the official upstream repo
[QianWen] Check for qianwen-ai updates and notify the user when a new version is available. TRIGGER when: user asks to check for updates, check version, asks 'is there a new version', 'latest version', 'update skills', 'check update', or any other qwen skill delegates to this skill, or user explicitly invokes this skill by name (e.g. use qianwen-update-check). DO NOT TRIGGER when: non-update-related tasks, general version questions about other software.
Use when checking live Capy task or PR state through Brave, Computer Use, or a Capy browser panel.
Retrospective audit of recently merged/closed PRs for anomalies that slipped through - merges without green builds, merges onto red main, unresolved or post-merge review threads, hollow resolutions. Read-only sweep, then confirmed remediation (issues, disposition replies). Use when asked to sweep PRs, audit merged PRs, or check what slipped through.
Use for stacked PRs with the gh-stack extension: creating, viewing, editing, pushing, submitting, syncing, rebasing, merging, or checking out a stack, or splitting multi-part work into reviewable layers. Also use whenever a stack is checked out or the user mentions stacks, branch layers, or dependent PRs.
Monitor a pull request for CI failures, review comments, and merge conflicts — then fix them automatically. Use when a PR is open and you want the agent to keep it merge-ready.
Scout the current work and recommend the next skill or action. Arguments: repo (whole-repo health), issue (deep implementation plan for an issue), milestone (milestone readiness and issue set). With no argument, read git logs and local branch state first to set scope, then suggest what to do next. Use when the user asks to recon, scout, assess, or "what should I do next". Knows DecisionNerd/dev-skills: agents, architect-it, idk-now, kiss, repos, issues, milestones, pulls, check-readiness, merge-it, fix-it, test-it, observe-it, document-it, research-it, refactor-it, troubleshoot-app, diagnose-bug, tidy-up. Prefer idk-now when the user is lost or needs vision-tied coaching across DocSlime / ProductFeeling / Impeccable / vendored skills — not only this pack.
Install, discover, remove, and update agent skills using the npx skills CLI. Use when asked to install a skill, add a skill from a repo, find or search for skills, list installed skills, remove or uninstall a skill, update skills, or check for updates. Triggers on: "install X skill", "add the Y skill", "find skills for Z", "what skills are available", "remove skill", "update my skills", "check for skill updates", "search for a skill that does X".
Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue.
Report a bug in the compound-engineering plugin
This skill should be used when a designer wants to produce a holistic design for a full feature before it is broken into tasks — for example "design feature