Loading...
Loading...
Found 164 Skills
Use when a PR is submitted and ready for peer review, to evaluate another agent's work against task requirements and code quality standards
Use when running the automated security alert fix pipeline — opens fix PRs, creates issues for breaking changes, dismisses false positives.
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
Investigate a GitHub issue — fan out parallel exploration, find the root cause (5 Whys, evidence-backed), and write a reviewable RCA artifact (then post a summary to the issue). The investigate step before piv-implement-issue. Use to diagnose a bug/issue before fixing it.
Use when a PR has merge conflicts with its base branch, including conflicts found during babysitting or merging.
Use when asked to "merge all open PRs" or land the open PRs together. Snapshots the open set, builds one gh stack, resolves conflicts, and merges once.
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
Monitor a pull request for CI failures, review comments, and merge conflicts — then fix them automatically. Use when a PR is open and you want the agent to keep it merge-ready.
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue.
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
Use for stacked PRs with the gh-stack extension: creating, viewing, editing, pushing, submitting, syncing, rebasing, merging, or checking out a stack, or splitting multi-part work into reviewable layers. Also use whenever a stack is checked out or the user mentions stacks, branch layers, or dependent PRs.