bmad-story-cycle
Full epic development cycle: all stories implemented, verified, reviewed, and merged in sequence. Use when user says "dev epic N", "run story cycle", "implement epic [N]", or "story cycle [N.M]" to resume from a specific story.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing PRs, use github-pr-merge instead.
ci-analysis
Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked "why is CI red", "test failures", "retry CI", "rerun tests", "is CI green", "build failed", "checks failing", or "flaky tests".
babysit-pr
Babysit a GitHub pull request after creation by continuously polling CI checks/workflow runs, new review comments, and mergeability state until the PR is ready to merge (or merged/closed). Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and stop only when user help is required (for example CI infrastructure issues, exhausted flaky retries, or ambiguous/blocking situations). Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.
change-reaudit
Re-audit code changes to identify side effects, regression risks, and unhandled edge cases before merging or deploying.
git-branch-cleanup
Analyzes and safely cleans up local Git branches. Categorizes branches by merge status, staleness, and remote tracking. Provides interactive selection with safety guards. Use when the user wants to clean up branches, delete old branches, organize Git branches, or asks about which branches can be safely deleted.
zenml-backport
Backport docs/examples changes to a pre-existing ZenML release. Use when changes merged to `develop` need to be reflected in a live release version. Triggers include "backport", "cherry-pick to release", "update release docs", or when docs/examples changes need to be applied to an existing release branch.
ironclaw-workflow-orchestrator
Install and operate a full GitHub issue-to-merge workflow in IronClaw using event-driven and cron routines. Use when setting up or tuning autonomous project orchestration: issue intake, planning, maintainer feedback handling, branch/PR execution, CI/comment follow-up, batched staging review every 8 hours, and memory updates from merge outcomes.
agentic-merge-upstream
Merge upstream changes from the official Copilot SDK into this Java SDK.
backpack-code-review-checklist
Comprehensive code review checklist for Backpack design system components. Use when: (1) Reviewing PRs for new or modified Backpack components, (2) Validating component compliance with Constitution and design system rules, (3) Checking if component follows Backpack conventions before merge, (4) Identifying violations in API design, token usage, accessibility, or documentation. Covers Constitution principles (I-XIII), decisions/ guidelines, API encapsulation rules, private token restrictions, design approval workflow, icon alignment helpers, hover mixin usage, token semantic correctness, and snapshot currency. Essential for maintaining Backpack quality standards and catching non-obvious violations like className props in new components, wrong icon alignment wrapper, raw :hover instead of bpk-hover mixin, or cross-component private token usage.
pragmatic-clean-code-reviewer
Strict code review following Clean Code, Clean Architecture, and The Pragmatic Programmer principles. Use when: (1) reviewing code or pull requests, (2) detecting code smells or quality issues, (3) auditing architecture decisions, (4) preparing code for merge, (5) refactoring existing code, or (6) checking adherence to SOLID, DRY, YAGNI, KISS principles. Features a 3+4+2 questionnaire system to calibrate strictness from L1 (lab) to L5 (critical). Also triggers on: "is this code good?", "check code quality", "ready to merge?", "technical debt", "code smell", "best practices", "clean up code", "refactor review", "review this PR", "PR review", "code review", "pre-merge check", "code audit", "is this production-ready?", "find bugs", "look at my code", "check for issues".
merge-worktree
ìí¬í¸ë¦¬ ë¸ëì¹ë¥¼ mainì¼ë¡ squash-merge + conventional commit ìë ìì±. codex-swarm ìí¬í¸ë¦¬ ìë ì¸ì. '머ì§í´', 'merge worktree', 'ìí¬í¸ë¦¬ 머ì§', 'ê²°ê³¼ ìì§', 'squash merge' ìì²ì ì¬ì©.
Jujutsu Version Control
Use jujutsu (jj) for all version control operations including commits, branches, merges, rebases, and repository management. Handles git workflow translation to jj equivalents.
check-pr
Checks a GitHub pull request for unresolved review comments, failing status checks, and incomplete PR descriptions. Waits for pending checks to complete, categorizes issues as actionable or informational, and optionally fixes and resolves them. Use when the user wants to check a PR, address review feedback, or prepare a PR for merge.
diffusion-perf
Deprecated alias (merged into diffusion-kernel).
auto-mr
Push current branch, create MR/PR, wait for CI pipeline, merge, and clean up branch using auto-mr CLI
git-spice-merge-my-stack
Merge a stacked git-spice branch chain with gh by retargeting each PR to main and merging bottom to top, including conflict recovery via rebase.
code-change-verification
Verify code changes by identifying correctness, regression, security, and performance risks from diffs or patches, then produce prioritized findings with file/line evidence and concrete fixes. Use when reviewing commits, PRs, and merged patches before/after release.
SWE-Manager â Autonomous Engineering Manager
You are the SWE-Manager, an always-on autonomous engineering manager for the SWE-Squad system. You operate as a persistent pi-agent session with 16 custom tools. You do NOT write code yourself â you delegate all investigation, development, review, testing, and merging to configured engines via the
fetch-milestone-prs
Fetches all merged pull requests for a given GitHub milestone and saves their metadata as individual JSON files. Use this skill when asked to retrieve PRs for a milestone, gather PR data for release notes, or collect milestone PR metadata.
agents-md-sync
Analyze code changes on the current branch and recommend updates to AGENTS.md files that have become stale. Use this skill before creating a PR, when the user asks to check AGENTS.md freshness, or when preparing an AGENTS.md update after a PR merges to main. Trigger whenever the user mentions syncing, updating, or checking AGENTS.md files, or when they're about to create a PR that touches code structure (new modules, renamed directories, changed commands, modified architecture).
ccpm
CCPM - spec-driven project management: PRD â Epic â GitHub Issues â parallel agents â shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync the X epic', 'push tasks to github'), starting work on an issue ('start working on issue N', 'let's work on issue N'), analyzing parallel work streams, running standups ('standup', 'run the standup'), checking status ('what's next', 'what's blocked', 'what are we working on'), closing issues, or merging an epic. Use ccpm any time the user is talking about shipping a feature, managing work, or tracking progress â even if they don't say 'ccpm' or 'PRD'. Do NOT use for: debugging code, writing tests, reviewing PRs, or raw GitHub issue/PR operations with no delivery context.
pyroscope-dotnet
Summarize an upstream merge PR with diff overview and profiler-related commit log
PDF Kit
AI-powered PDF tools: fill forms, merge, extract data, and split PDFs
bible-merger
Merge multiple book analyses into a unified bible. Use after analyzing several books from a series to consolidate characters, style patterns, and structure into a single canonical reference.
/review-pr - Maintainer-style PR review bot
You are a strict, opinionated maintainer of the Alpine.js project. Your job: review a PR, fix what you can, push fixes, and post a verdict comment so Caleb can just merge or close.
dep-update
Review, merge, and release dependency update PRs. Merges green dependabot PRs, closes stale/failing ones, runs full verification, and publishes a patch release.
superplane-changelog
When generating a SuperPlane changelog from merged commits. Use for "what's new" summaries with new integrations, new components/triggers, improvements, security updates, and bug fixes. Output is user-focused markdown in tmp/.
gitlab
Manages GitLab merge requests, CI/CD pipelines, and issues via glab CLI. Load before running glab commands, creating MRs, debugging pipeline failures, checking CI status, or any GitLab operation. Triggers on "merge request", "pipeline", "CI failure", "glab", or when git remote contains "gitlab".
git-worktrees
Work with git worktrees for isolated parallel development. Use when starting feature work in isolation, when need separate workspace without branch switching, or when cleaning up worktrees after PR merge.
Epublys
EPUB/PDF tools: merge, split, compress, convert, edit metadata, validate ebooks.
codereview
Use when you need a comprehensive code review combining architecture, security, and test perspectives - especially before merging, releasing, or after major changes.
agent-scan-guard
Use when you need to run security checks for MCP and agent workflows before merging changes in shared repositories.
github-assistant
GitHub workflow automation using `gh` CLI. Use when creating PRs, reviewing code, managing issues, auto-replying to fixed issues, adding comments, assigning users, managing labels, merging PRs, or checking CI status. Includes auto-reply script and Vietnamese templates.
markless
Cut a release - run checks, bump version, merge PR, tag, and publish to crates.io
decision-triage
Interactively walk through every decision log in `.ninthwave/decisions/` one at a time. For each log: read it, check whether the choice it describes still matches what shipped, ask the human what to do (ratify / record as ADR / codify into an existing doc / create follow-up work item / revise / merge / skip), execute the decision, and delete the log. This is the canonical way to clear the decisions inbox: a synchronous, human-in-the-loop session. Use when asked to "triage decisions", "review decision logs", "clear the decisions inbox", or "walk through decisions".