Loading...
Loading...
Found 2,777 Skills
Quick status check for current branch and PR state showing local changes, CI results, reviews, and merge readiness. Use when user wants branch status, PR state, CI check results, review status, or merge readiness. Use for "pr status", "what's the status", "is my PR ready", "check CI". Do NOT use for creating PRs, pushing changes, or fixing review comments.
Agent skill for code-review-swarm - invoke with $agent-code-review-swarm
Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.
Use when starting a new feature branch, creating isolated development environments, or working on multiple tasks simultaneously without stashing or switching branches. Triggers: user says "worktree", "new branch for work", "parallel development", "isolated environment", needs to work on two things at once.
Use anime-style multi-role continuous conversational code review to output review opinions with natural technical anchors through strong character interaction
Remove a future phase from roadmap and renumber subsequent phases
Send Discord messages and notifications via webhook. Use when you need to post alerts, updates, or messages to Discord channels without full bot setup.
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
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
Initialize a new project — repo, structure, CI, and first commit
Create well-formatted conventional commits in a repository hosted on Azure DevOps (ADO / Azure Repos). Use this whenever the user asks to commit changes and the project is on Azure DevOps — dev.azure.com, visualstudio.com, or explicit mentions of ADO, Azure Repos, or work item IDs like `AB#1234`. Automatically appends `AB#<id>` work-item trailers when the branch name or staged changes reference one, and attributes AI-assisted authorship.
Automate Pulumi provider repo upgrades with the `upgrade-provider` tool. Use when upgrading a pulumi provider repository to a new upstream version, running `upgrade-provider`, and addressing its common failure modes like patch conflicts or missing module mappings.