Loading...
Loading...
Found 2,521 Skills
Activates a work item or issue and creates the feature branch in one step. Supports ADO work items and GitHub issues, selected via the ISSUE_TRACKER config setting. Use when the user says "start story", "start working on", "begin AB#N", "kick off AB#N", "start issue
Write a concise GitHub pull request body with five headings. The headings are Background, Design Decisions, Changes, Verification Performed, and Post-Merge Operations. When you create, open, submit, or update a pull request, use this skill. Use it for a PR description or for gh pr create. Do not use this skill for commit messages alone.
Monitor an open GitHub PR every two minutes, optionally use Copilot review, resolve feedback, and request human review only when ready for merge or blocked.
Use when named or when the user requests additional context for code review. Review Bitbucket/GitHub PRs or local changes using TWG context, create JSON and Markdown, and post only when requested.
Write the release notes for a Playwright release - the Node.js notes in docs/src/release-notes-js.md together with the Python, Java and .NET translations, and the GitHub markdown for each language's release. Use when asked to write, translate or publish release notes.
End-to-end release cutting for a GitHub repo: decide the next semantic version from the Conventional Commits since the last tag, draft proper release notes (GitHub auto-generated via `.github/release.yml`, or hand-curated grouped by change type with highlights and upgrade notes for breaking changes), create and push an annotated tag, publish the GitHub release, and optionally update `CHANGELOG.md`. Use when the user says "cut a release", "tag a release", "publish a release", "ship vX.Y.Z", "bump the version", "what version should this be", "write the release notes", "draft the changelog", or invokes /release. Distinct from /gh-bootstrap (which scaffolds the `.github/release.yml` + release workflow plumbing once): this skill runs the actual release ceremony — version decision, notes, tag, publish. Run after the work is merged to the default branch.
Uploads local images and short videos (mp4, mov, webm) through GitHub's attachment pipeline and writes one verified Screenshots section into a PR body. Use when the user says "attach screenshots to the PR", or when the user explicitly asks to add or attach screenshots to a PR. Never infer from local images. Not for capturing screenshots; use capturing-screenshots.
Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line. Use when you have a list/JSON of review findings (each with a file path, line number, and a message such as summary/failure_scenario) and want them published on a PR as inline review comments. Triggers include "post these review comments on the PR", "associate comments to files in the PR", "publish review findings to PR
Audits a repository's GitHub Actions workflows for CI optimization opportunities — missing caches, redundant setup, sleep-based readiness, long test jobs without sharding, full-history checkout, dead env vars, build-cache misconfig, and ~60 more patterns across caching, redundancy, parallelization, conditional execution, trigger scope, and hidden failures. Use when: (1) analyzing a repo's CI for optimization opportunities, (2) producing a prioritized report with measured wall-clock and runner-minute savings, (3) re-auditing after upstream CI changes. Do not trigger for: general CI setup help, writing new workflows from scratch, non-GitHub-Actions CI systems, or security/posture audits — use `ci-secure` for those.
Organize checkout/worktree topology, dependent branch/PR stacks, and unified delivery boundaries for change workstreams using Git/GitHub: identify normalized repositories and isolate regular implementations with an owning worktree by default, with worktree also permitted by default for explicit PR requests; determine commit, push, and PR actions in order of user-specified explicit endpoints, default Draft PR for normalized repositories, and local-only default for non-normalized repositories; publish safely from main/master; follow up on conflicts, CI status, and local commit/push for existing PRs. Applicable to worktree creation, migration, secure cleanup, "branch already checked out" scenarios, post-implementation Git delivery, splitting stacked/dependent PRs, using `gh stack` to create, view, sync, or land stacks, as well as PR merge conflicts, failed checks, fixing PRs to mergeable state, and uncommitted or unpushed fixes. It only owns Git topology and delivery, and does not take over domain implementation or project design; the exact syntax of `gh stack` is discovered from local `--help` output. Default delivery does not grant authorization to implicitly switch the main working tree branch, mark as Ready, merge, retarget, release, or force-push.
Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
Mentor a reviewer through a pull request step by step, teaching the code as it goes, and post the agreed findings as one GitHub review in their name.