Loading...
Loading...
Found 581 Skills
Author-side PR lifecycle babysitter and companion to review-pr. Use when the user wants to tend an existing GitHub PR through CI, review threads, description sync, mergeability, auto-fixes, or asks to babysit a PR with or without an existing manifest.
Walk through a PR or large diff together — your own or someone else's — one sub-changeset at a time and one review topic at a time within it. Use when reviewing a substantive PR collaboratively, walking a large refactor, or when the user asks to walk a PR, walk a diff, explain a PR, review collaboratively, or review a change together. Optional --canvas runs the walk in a live HTML artifact.
Run one exact Ticket through recovery and autonomous work to a ready pull request, keeping its Manifest, progress and completion record on that same Ticket, and land it only when told to. Use when orchestrate, an agent runner, or a person supplies a specific issue, tracker item, or file Ticket to work end to end. This skill does not select backlog work or enforce Auto eligibility at dispatch.
Autonomous PR review that posts high-signal, human-voiced comments under your account. Use when reviewing someone else's PR or your own manifest-driven PR, when you want a precision-tuned review you can walk away from, or when the user asks to review a PR, post a PR review, autoreview, loop review, or watch a PR.
Called by review-pr after its reviewer fleet and judgment pass return: consolidates their findings against the PR's history into the set of comments worth posting — pruning what the PR already covers, merging duplicates, subordinating defects under premise questions, bounding to the reviewed range, and rewriting every body in the caller's voice. Not for direct use.
Called by review-pr in both modes: independently judges whether landing the whole change serves the project after its material consequences are considered. Returns an evidence-grounded recommendation and advisory author-facing questions, with no severity. Not for direct use.
Perform code reviews. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
Integration or handoff decision for verified work, based on actual Git state and evidence. Use when verified work is ready for merging, pushing, opening a pull request, preserving or discarding a branch, or cleaning up its workspace.
Generate and maintain the system recap block in a PR description - a GitHub-rendered visual summary of which system primitives a change touches, how risky it is, and what changed. Prefer mermaid sequence diagrams for the change; pick another graph type when it explains the diff better. Use when planning a non-trivial change (plan mode), when creating or updating a pull request (recap mode), or when the user asks for a visual recap, visual plan, system review, or PR recap.
Watch a pull request through CI and human review, fixing real failures and findings. Use when asked to monitor, watch, or babysit a PR.
Review a pull request with independent agents when it has no review yet, settle its open review comments from reviewers and people and its failing CI checks, and check each round of fixes with an independent reviewer before pushing, until every thread is answered and the required checks pass, or a problem needs the user. Use when the user asks to babysit or watch a PR, to handle, address, or settle its review comments, or to fix its failing checks, or when another skill hands over a newly opened PR.
Merge pull requests into the main branch in dependency order, review the whole release for rollout problems, promote it through each deployment branch with pull requests, and run pending migrations at the correct point for each environment. Use when the user asks to merge and release pull requests through every environment and run their migrations.