Loading...
Loading...
Found 3,740 Skills
Stage all changes, generate a descriptive commit message from the diff, commit, and push to the current branch's upstream.
This skill applies when the user wants to resume previous work, enters the command "/vibe-continue", or starts a new session and needs to load saved context. Restore from shared task facts first, then use task.md as the local handoff.
Create a PR title and draft description after substantive code changes are finished. Trigger when wrapping up a moderate-or-larger change (runtime code, tests, build config, docs with behavior impact) and you need the PR-ready summary block with change summary plus PR draft text.
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.
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.
Agent skill for code-review-swarm - invoke with $agent-code-review-swarm
Verifies the agent's current work against a specific question by analyzing unstaged changes, staged changes, recent commits, and codebase context. Answers succinctly for a senior audience. Use when user says "/check", "verify that", "confirm that", "check if", "is X done?", or asks about current session changes.
This skill should be used when the user asks to "execute this blueprint", "run the plan", "execute the plan", "start building from the plan", "implement the blueprint", "implement the plan", "continue the plan", "resume execution", or "execute 01_milestone_name.md".
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.
Inspect unresolved review threads for the current pull request, then reply to and resolve them as needed.
Release vercel-plugin — run gates, bump version, generate artifacts, commit, and push. Use when asked to "release", "ship", "bump and push", or "cut a release".
Project status dashboard — open issues, recent commits, active branches/worktrees, memory state, and scratchpad. Use when the user asks for a status report, project overview, "what's going on", "where are we", or wants to catch up on project state without the full /catchup reconstruction.