Loading...
Loading...
Found 193 Skills
Use when replying to an issue reporter or outside contributor, or reviewing someone else's pull request.
Watches a pull request through CI and review, fixes real findings and stops when it is ready, merged or blocked. Use when the user asks to watch, monitor or babysit a PR, or /ds-watch-pr.
Files a short, clear pull request for the current branch. Use when the user asks to open, file or create a PR, or says /ds-pr.
User-triggered Enterprise PR recorder for a completed phase. Stacked plans publish their phase branch through the publish-phase repair command; other plans create or reuse the current-branch PR. Links the tracked issue and records PR identity. It never posts review verdicts, never rebases, and never force-pushes.
Write a branch's PR body that tells a reviewer how much attention it needs, with a visual summary, harvested evidence and a fresh-context one-way or two-way door call, then put it and an attention label on the branch's PR. Use when a branch is ready for review, when the user says "write the PR body", "update the PR description", "how risky is this PR", or "is this ready to merge", and when another skill closes a branch.
Attach image and video media to GitHub pull request descriptions or issue and pull request comments with the GitHub CLI on GitHub.com and GHE.com.
Review a GitHub pull request by URL using the review-team skill. Outputs copy-pasteable conventional comments with line references and code suggestions. Uses a personal voice profile by default — swap skills/shared/pr-review-voice-marco.md for your own. Use when the user shares a PR URL, asks to review a PR, or mentions "review pr".
Create pull requests using GitHub CLI with proper templates and formatting
Add line-specific review comments to pull requests using GitHub CLI API
File a concise pull request. Use when the user asks to file, open, or create a PR.
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
Use when the user asks to list, show, or review open issues — from the tracker recorded in docs/agents/issue-tracker.md, whether GitHub, Jira, local markdown, or another backend, or from a repository or project the user names. Read-only: not for creating, editing, closing, or triaging issues.