Loading...
Loading...
Found 194 Skills
Finish a PR by repeatedly requesting a Kelos review, waiting for its check, addressing valid review findings, squashing commits, and updating the PR until a review approves and that iteration is finalized. Use when the user says "finish-pr" or asks for this review-and-fix loop. Defaults to the PR for the current branch.
Drive an open tester-army/e2e PR through conflicts, review bots, and CI until it is green with every thread handled, then label it Ready for Human Review. Use after opening a PR, or when asked to babysit, watch, monitor, check on, or get a PR green.
Triage GitHub Copilot's automated PR review comments, fix the confirmed issues, and resolve the review threads. Use when the user mentions Copilot review findings/comments, asks to address or clear PR feedback, or wants Copilot's review threads resolved.
Take a PR from review to merged — run the repo's code-review skill on it in a loop (review, fix, re-review) until nothing is left to fix, applying ALL fixes on the PR branch, wait for CI green, then squash-merge. Use when asked to "ship it", "ship PR
Use for version bumps on explicit request or as the pre-merge step of a PR land. Never infer from finished, reviewed, green, or draft-ready work. Assigns SemVer.
The domain expert's product manager in a project repository run by the Boring Factory. Use when the expert brings a need or an idea, wants to clarify, change or resume a feature ("reprends la fiche"), asks what is happening with a feature, has a builder's question to answer, or has a preview to try and accept. Interviews one question at a time, writes the contract and mockups on the contract pull request, and submits the expert's approval only after the expert confirms. Never writes code.
This skill is used to attempt to merge in pull requests opened by Renovatebot, but which are not automatically merged.
Splits a large change into stacked pull requests with GitHub's gh stack CLI. Use when the user says "stack PRs" or "create a PR stack", or when a change is too big to review as one PR, has dependent parts, or overlaps the same author's open PRs, or when creating, updating, syncing, merging, or recovering a gh stack stack.
Watches the user's own PR in a bounded loop, triaging new review feedback and reporting failing CI, or re-running or fixing it when granted, until approval, then hands off to landing-prs without merging, even when asked to merge once approved. Use when the user says "watch this PR", or when the user explicitly asks to watch their PR for feedback or CI, including a watch that should merge on approval. Never infer from an open PR. Not for a PR the user reviewed; use watching-reviewed-prs.
Pull request: use when a PR needs opening, or commits sit on main and need moving to a named branch.
Use when writing or editing a pull request title or body.
You MUST use this before running a project-scoped GitHub CLI command (gh pr, issue, repo, api, release, run) against github.com, again before every later gh command in the same session, after a gh command fails with an access error such as "Could not resolve to a Repository", and when asked to check or switch the gh account for the current project. It switches gh to the already logged-in account named by GH_ACC in the project's .env/.env and reports the switch in one line. Not for plain git or SSH operations, gh help or version output, logging in, or hosts other than github.com.