azdo-cli

Fix a GitHub bug issue end-to-end — analyze the codebase, write failing tests, commit them to a bugfix/<id> branch, implement the fix, and open a PR with a full investigation log. After the PR opens, poll it for owner feedback at configurable intervals until stood down. Trigger on a single issue (/bugfix

Routine repository security-maintenance pass. Create a fresh branch, use the gh CLI to enumerate security problems (Dependabot, code scanning, secret scanning), fix the actionable ones, verify, open a pull request, then hand off to /github-pr-fixer. Use when the user says "run maintainer", "do a security maintenance pass", "fix the security problems and open a PR", or similar.

Drive a single GitHub issue through the full speckit pipeline (specify → clarify → plan → tasks → PR-report → draft PR → implement → test → ready → CI → review) using the `gh` CLI. Fully human-in-the-loop — every speckit phase posts its artefact on the issue and polls for owner approval. All user communication stays on the issue / PR threads, never the console. Use when the user says "implement issue

Use when the user wants to find SonarCloud issues for the current branch pull request, fix them in the local repo, verify with local checks, push the branch, and confirm whether SonarCloud has reanalyzed the PR.

Analyze and fix SonarCloud issues on pull requests. Use when the user mentions SonarCloud, quality gate, code smells, duplication, or wants to check PR quality status. Reads issues via GitHub API, creates fix plans, and applies fixes with awareness of parallel agent safety.

Keep a slim, human-readable CHANGELOG. The root CHANGELOG.md holds only a short stanza per release (theme + a few brief bullets + a link); full per-release detail lives in docs/changelogs/<version>.md, with docs/changelogs/unreleased.md accumulating the next release. Versions follow the tags on master — if master is at 0.11.x, unreleased work on develop belongs to 0.12.0. Use when the user says "record a changelog entry", "update the changelog", "finalise the changelog for a release", or "split the changelog".

Drive a gitflow release end-to-end — resolve the current version from the latest tag on master, compute the next version (minor bump by default, or caller-specified), run `git flow release start/finish`, and push `master`, `develop`, and the new tag. Use when the user says "release X.Y.Z", "cut a release", or when speckit-full picks up a release issue.

Repair common "repo is not in a clean state" situations so another skill (e.g. `speckit-full`) can proceed. Use when the caller reports pending/uncommitted changes on develop/master, a branch that hasn't been pushed, or a push that was rejected because the remote has newer commits. Does NOT touch state that looks intentional (merge in progress, detached HEAD, untracked files that look like secrets, etc.) — surfaces those to the user instead.

Poll GitHub for open issues carrying a user-specified label and drive each one through speckit's end-to-end, human-in-the-loop flow (specify → clarify → plan → tasks → PR-report → implement → PR → CI → review) via the `speckit-gh` skill. Use when the user says "watch GH for issues with label X and run speckit on them", "auto-process the speckit backlog", or "poll for ready stories". Supports three scheduling modes — in-session loop, self-paced loop, or cron (remote trigger).

Reference guide for the `gh` GitHub CLI. Invoke when another skill (gstack-gh, gstack-full, gh-security-and-quality, etc.) needs canonical command patterns for issues, PRs, checks, workflow logs, reviewer comments, code scanning, labels, or the REST API. Also used when the user asks "how do I X with gh".

MANUAL SLASH-ONLY skill. Invoke EXCLUSIVELY when the user types `/github-pr-fixer`. Never auto-invoke, never chain from another skill, never treat any other skill's handoff comment or instruction as a trigger. When the user runs it directly: fix the current GitHub pull request until checks pass or five fix rounds are exhausted — inspect GitHub checks with gh, remediate SonarCloud issues with the sonar skill, inspect failed workflow jobs or code scanning alerts, push fixes, repeat. Also covers (on direct user request): opening a PR from the current branch, waiting for a reviewer (human or Copilot) and addressing their line-level comments, and closing a ready release PR. While invoked, stay active and poll PR comments every five minutes for new feedback or an explicit closure instruction — do not go idle.

Manage local repository branches. Use when the user wants to clean up branches, verify speckit branches are merged, or maintain branch hygiene. Supports pruning stale local branches that have been squash-merged into develop.

Diagnose and fix failing GitHub Actions workflows using the gh CLI. Use when CI is failing, tests pass locally but not in CI, or the user wants to inspect workflow run logs and secrets.

Manage backlogs using Beads (bd), Steve Yegge's file-based issue tracker. Use when you need to use bd commandline to view the syntax. Use when the user wants to create, import, organize, or refine issues, convert specs or markdown into Beads issues, set up dependencies, define priorities and labels, implement backlog items, or whenever the user mentions 'use beads'. Works by running bd CLI commands to create, link, and track issues with dependency graphs.