Loading...
Loading...
Found 587 Skills
Orchestrate an explicit GitHub ticket workset through parallel Codex tasks.
Attach screenshots, recordings, and other media to GitHub issues, pull requests, and comments with `gh --attach`. Use whenever an issue, PR, or comment should carry an image or video the session captured or was given.
List and show Gitea/Forgejo pull requests — filters, fields, detail views, and finding PRs needing review.
Triage and review open GitHub issues and PRs against project templates and contribution guidelines.
Take finished work to a merge-ready PR in one pass - intent, review, live test, docs, lint, PR, and CI. User-invoked only - run /ship-it [wip|prod] ["intent"], or /ship-it on a branch with an open PR to resume or babysit it.
Monitor a pull request through review and CI. Use when the user asks to monitor, watch, or babysit a PR.
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.
Review and resolve open review feedback on a pull request against its upstream repository, then keep the branch in sync without rewriting history. Use when asked to "review my PR", address PR/review comments, respond to reviewer feedback, resolve review threads, or sync a feature branch with upstream before review. Covers: resolving the upstream remote (from git remote -v when not configured), challenging vs. fixing each comment, replying to and resolving threads with gh, and detecting/handling a branch that is behind upstream main (conflict check, user confirmation, no force-push).
Use when you need to request a code review for a PR/MR and want a consistent review brief (context, scope, risk areas, test instructions, acceptance criteria) before merge.
ALWAYS use this skill when creating or updating pull requests — never create or edit a PR directly without it. Follows Sentry conventions for PR titles, descriptions, and issue references. Trigger on any create PR, open PR, submit PR, make PR, update PR title, update PR description, edit PR, push and create PR, prepare changes for review task, or request for a PR writer.
Diagnose what state one open PR is actually in — unfinished plan steps, missing review, unresolved conversations, red CI, base conflicts, missing QA evidence, merge-ready — then run the matching chain of om-* skills in order and publish a status report. Use for "finish PR 123", "what is left on PR 123", "drive PR 123 to the end".
Record browser or Web UI interaction demos as optimized GIFs using the available browser tooling, state-based frame capture, and deterministic encoding, then publish to a dedicated assets branch when the task includes attaching the GIF to a pull request. Use when asked to make, record, or generate a GIF that demonstrates a browser workflow, and for every pull request that changes product-user-visible GUI behavior, which MUST include a GIF recorded from the pull request's real server and data flow.