Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From specclaw
Interactive Azure DevOps authentication setup: prompts for org, project, repo, validates a PAT, and saves credentials to .specclaw/.env. Run once per project before using PR-related commands.
How this skill is triggered — by the user, by Claude, or both
Slash command
/specclaw:auth-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).
Interactive Azure DevOps authentication setup. Guides the user to create a PAT, validates it, and saves credentials.
The user must run this command themselves in a real terminal — specclaw-auth-azdo refuses to run without /dev/tty because it prompts for a Personal Access Token. If you (the agent) try to invoke it, the script exits with instructions for the user. Just tell the user to open their shell and run specclaw-auth-azdo .specclaw directly.
specclaw-auth-azdo .specclaw
https://dev.azure.com/<org>/_usersSettings/tokens to create a PAT.config.yaml under the azdo: section; token to .specclaw/.env (gitignored)./specclaw:pr-azdo <change> as the next step.npx claudepluginhub chan4lk/specclaw --plugin specclawCreates 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.
Manages Azure DevOps resources via CLI: projects, repos, pipelines, builds, PRs, work items, artifacts, service endpoints.
Validates Azure DevOps projects, area paths, and teams from .env config, auto-creating missing resources. Supports project-per-team, area-path-based, and team-based strategies for ADO integration setup and troubleshooting.