From specclaw
Creates Azure DevOps pull requests for verified changes, including validation, PR creation via ADO REST API, and project context updates. Use when the project uses Azure DevOps instead of GitHub.
How this skill is triggered — by the user, by Claude, or both
Slash command
/specclaw:pr-azdoThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**First, run** `specclaw-ensure-init .specclaw` — idempotently creates `.specclaw/` if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
Create an Azure DevOps PR for a verified change.
specclaw-validate-change .specclaw <change> pr. Fails if verify-report.md is missing.specclaw-azdo-pr .specclaw <change> — always create the PR through this script, never hand-roll the ADO REST call. specclaw-azdo-pr stages and commits the full .specclaw/changes/<change>/ planning trail (proposal, spec, design, tasks, status, verify-report) into the branch and aborts if any of it is left uncommitted — bypassing it ships a PR missing the proposal artifacts.
AZDO_TOKEN, AZDO_ORG, AZDO_PROJECT, AZDO_REPO (set via /specclaw:auth-azdo)./specclaw:pr — prompts once, enforces on all runs.proposal.md, description from spec.md + verify-report.md, calls ADO REST API.**ADO PR:** <url> to status.md..specclaw/context.md to incorporate decisions from this change:
specclaw-update-context .specclaw <change> — this outputs an LLM prompt.context.md in place (architecture-doc style: replaces stale info, merges new decisions).context.md changed, commit it: git add .specclaw/context.md && git commit -m "docs(context): update project context after <change>" and push.CI outer loop (if loop.ci_gate: true): once the PR branch is pushed, the CI tier of /specclaw:loop (Step 3 / specclaw-loop ci-poll) polls Azure Pipelines runs and iterates fixes until they are green, or loop.ci_max_iterations / loop.ci_timeout_seconds halts and escalates. This is a cross-reference only — PR creation above is unchanged, and nothing extra runs when loop.ci_gate is false.
npx claudepluginhub chan4lk/specclaw --plugin specclawCreates a GitHub pull request for a verified change, reading verify-report.md and enforcing test policy. Run after /specclaw:verify.
Discovers, triggers, monitors Azure DevOps pipelines for repo/branch. Auto-diagnoses failures from logs, applies fixes, commits/pushes, re-triggers until success or max retries. Validates PR existence and description.
Discovers, triggers, monitors, and auto-fixes Azure DevOps pipelines (PR, Buddy Build, Release) for current repo/branch. Diagnoses failures from logs, applies fixes, commits/pushes, re-triggers until success or max retries. Validates PR existence and description.