Loading...
Loading...
Found 581 Skills
Gate a PR's merge without human review, and merge it when the gate passes. Use when landing a PR during autonomous work, or when another skill needs a merge gate.
Use when the user asks to review a pull request, branch, commit, or work-in-progress changes for correctness, agreed requirements, and project standards.
Assess and update an old PR against its current base and architecture. Use when the user says modernize, rebase this PR, or bring an old branch up to date; recommend rework or closure when a rebase would preserve obsolete behavior.
Stack draft PRs for the tickets a still-open PR unblocks — the frontier computed as if that PR were merged, branched on its head — and hand each to Copilot. Use when the user wants to start tickets blocked by an open PR, delegate the issues a PR will unblock, or open stacked PRs on top of a PR.
Review a code change or PR from every angle in one pass: requirement compliance, correctness, security, over-engineering (what to delete), and reuse/efficiency. Use for implementation review, PR review, merge readiness, 'what can we delete', or 'simplify review'.
Gut-check a pull request — is it meaningful, worth adding, correct, and minimal — and give one recommend-* verdict.
Review a pinned Git diff on two independent axes — repository standards and spec/behavior fidelity. Use when asked to review a branch, commit range, or PR against a fixed point; report evidence-backed findings without changing code, including correctness risks when no spec exists.
Evaluate, prepare, and review contributions to GitHub repositories the user does not own, including discussions, issues, private vulnerability reports, and pull requests. Use it when incorporating feedback or findings into a contribution, preparing the next pull request in a contribution series, or making user-requested revisions to an existing pull request, including maintainer feedback after submission. Do not use for routine work in the user’s own repositories or ongoing monitoring after submission.
PDD bug workflow. Use when the person reports a bug, an error or a wrong result in a PDD project. Reproduce it, fix the prompt and tests (PR 1), then the code (PR 2) if asked.
current release-driven Operating ModelをGitHub Issues / Pull Requestsへmaterializeし、release sprint / dependency / review / durable delivery stateを扱う時に使用する。
Take over an existing PR, branch, or agent thread while preserving contributor credit and unrelated work. Use when the user says takeover, take over this work, or continue another agent's implementation.
Review pull requests and recent code changes across specialized lenses: general code quality, tests, error handling and silent failures, comments and docs, type design, and simplification. Use when the user asks to review a PR, review recent changes, check tests, check error handling, check comments, analyze types, simplify/refine an implementation, run "review-pr", or before merging phase PRs in the epic-dev workflow.