Azsdk Common Generate SDK Locally
Azure/azure-sdk-for-android
Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization.
Automatically fix Azure SDK CI/CD pipeline failures by applying code changes and verifying locally.
Install Azsdk Common Pipeline Fixer
$ npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-fixer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/azure-sdk-tools azsdk-common-pipeline-fixer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-fixer .claude/skills/azsdk-common-pipeline-fixer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "azsdk-common-pipeline-fixer" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-fixer into .claude/skills/azsdk-common-pipeline-fixer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-fixer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-fixerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-fixer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/azure-sdk-tools azsdk-common-pipeline-fixer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-fixer .agents/skills/azsdk-common-pipeline-fixer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "azsdk-common-pipeline-fixer" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-fixer into .agents/skills/azsdk-common-pipeline-fixer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-fixer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-fixer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/azure-sdk-tools azsdk-common-pipeline-fixer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-fixer .cursor/skills/azsdk-common-pipeline-fixer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "azsdk-common-pipeline-fixer" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-fixer into .cursor/skills/azsdk-common-pipeline-fixer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-fixer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Azure/azure-sdk-tools.git --path .github/skills/azsdk-common-pipeline-fixer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-fixer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/azure-sdk-tools azsdk-common-pipeline-fixer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-fixer .gemini/skills/azsdk-common-pipeline-fixer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "azsdk-common-pipeline-fixer" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-fixer into .gemini/skills/azsdk-common-pipeline-fixer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-fixer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Azure/azure-sdk-tools azsdk-common-pipeline-fixerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-fixer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-fixer .github/skills/azsdk-common-pipeline-fixer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "azsdk-common-pipeline-fixer" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-fixer into .github/skills/azsdk-common-pipeline-fixer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-fixer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-fixer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Azure/azure-sdk-tools azsdk-common-pipeline-fixer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-fixer .opencode/skills/azsdk-common-pipeline-fixer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "azsdk-common-pipeline-fixer" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-fixer into .opencode/skills/azsdk-common-pipeline-fixer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-fixer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
azsdk-common-pipeline-fixer- GitHub stars
- 134
- Token cost
- ~831 tokens
- SKILL.md length
- 304 words
- Files
- 2
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- MIT
At a glance
Automatically fix Azure SDK CI/CD pipeline failures by applying code changes and verifying locally.
- Works in 6 steps: Find analysis - Reuse an existing… → Classify - Fixable (test, type, lint,… → Locate - Identify the affected package,… → …
- : fix pipeline failure
- SKILL.md covers Rules, MCP Tools, Steps and Examples, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Azsdk Common Pipeline Fixer is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Automatically fix Azure SDK CI/CD pipeline failures by applying code changes and verifying locally. USE FOR: "fix pipeline failure", "fix CI", "fix failing tests", "auto-fix and commit the fix", "fix build error", "fix mypy/pylint/type-check/lint errors", "auto-fix pipeline", "resolve pipeline failure". DO NOT USE FOR: pipeline analysis (instead use azsdk-common-pipeline-analysis), API design review, SDK publishing. INVOKES: azure-sdk-mcp:azsdkpackagebuildcode, azure-sdk-mcp:azsdkpackageruncheck…
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/trigger.eval.yaml`). Compatibility notes: azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools
It sits in Backend & APIs, covering Failing and flaky tests, MCP servers and Type safety. It works with Microsoft Azure and Model Context Protocol. The repository describes itself as: Tools repository leveraged by the Azure SDK team. The licence is MIT.
When your agent uses it
- : fix pipeline failure
- Fix failing tests
- Auto-fix and commit the fix
- Fix build error
Example prompts
- “fix pipeline failure”
- “fix CI”
- “fix failing tests”
- “/azsdk-common-pipeline-fixer”
Requirements
- Python 3
- Compatibility (from SKILL.md): azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Find analysis - Reuse an existing analysis from the PR comments; if none, view the azsdk-common-pipeline-analysis skill.
- Classify - Fixable (test, type, lint, import, assertion errors) vs retry (infrastructure) vs escalate (breaking API, credentials).
- Locate - Identify the affected package, its path, and the files/lines to change.
- Fix - Read the failing code at the cited lines and apply the minimal fix.
- Verify - Run azsdk_package_build_code → azsdk_package_run_check → azsdk_package_run_tests on the package; all must pass. If the…
- Iterate & commit - On failure, revise and re-verify (max 3 attempts). Once all pass, commit with a descriptive message.
What it can do on your machine
Read from SKILL.md and the folder at commit 942ef24. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools
From compatibility in the SKILL.md frontmatter.
Context cost
Azsdk Common Pipeline Fixer loads about 831 tokens when it runs. Until then it costs about 152 tokens; SKILL.md has 304 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Azure/azure-sdk-tools at commit 942ef24, republished under its MIT licence (© Azure). 304 words, ~831 tokens.
Download SKILL.mdSave it as
.claude/skills/azsdk-common-pipeline-fixer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- azsdk-common-pipeline-fixer
- description
- Automatically fix Azure SDK CI/CD pipeline failures by applying code changes and verifying locally. USE FOR: "fix pipeline failure", "fix CI", "fix failing tests", "auto-fix and commit the fix", "fix build error", "fix mypy/pylint/type-check/lint errors", "auto-fix pipeline", "resolve pipeline failure". DO NOT USE FOR: pipeline analysis (instead use azsdk-common-pipeline-analysis), API design review, SDK publishing. INVOKES: azure-sdk-mcp:azsdk_package_build_code, azure-sdk-mcp:azsdk_package_run_check, azure-sdk-mcp:azsdk_package_run_tests, azure-sdk-mcp:azsdk_verify_setup.
- compatibility
- azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools
- license
- MIT
- metadata.version
- 1.0.0
- metadata.distribution
- shared
Pipeline Fixer
This skill automatically fixes Azure SDK CI/CD pipeline failures. It analyzes the failure, identifies the root cause, applies code changes, and verifies the fix locally using build, check, and test tools before committing.
Rules
- Requires the
azure-sdk-mcpserver and a local clone of the SDK language repo. - Work on the PR branch — the failing code is there, not main.
- Analyze first, then apply the minimal code change for the root cause.
- Verify ONLY via the azsdk MCP package tools (build → check → tests); never raw shell build/test commands.
- Never fix infrastructure failures (timeouts, crashes, throttling) — recommend retry. Iterate up to 3 times, then report.
MCP Tools
| Tool | Purpose |
|---|---|
azure-sdk-mcp:azsdk_verify_setup | Verify local environment is ready |
azure-sdk-mcp:azsdk_package_build_code | Build the package locally |
azure-sdk-mcp:azsdk_package_run_check | Run validation/lint/typecheck locally |
azure-sdk-mcp:azsdk_package_run_tests | Run tests locally |
Prerequisites: azure-sdk-mcp server required. Local clone of the affected SDK language repo. Language build tools installed.
Steps
- Find analysis - Reuse an existing analysis from the PR comments; if none, view the
azsdk-common-pipeline-analysisskill. - Classify - Fixable (test, type, lint, import, assertion errors) vs retry (infrastructure) vs escalate (breaking API, credentials).
- Locate - Identify the affected package, its path, and the files/lines to change.
- Fix - Read the failing code at the cited lines and apply the minimal fix.
- Verify - Run
azsdk_package_build_code→azsdk_package_run_check→azsdk_package_run_testson the package; all must pass. If the environment isn't ready, runazsdk_verify_setup. Never substitute raw shell build/test commands. - Iterate & commit - On failure, revise and re-verify (max 3 attempts). Once all pass, commit with a descriptive message.
Examples
- "Fix the pipeline failure for build 6447834"
- "My Python SDK CI is failing with a type error, fix it"
- "Auto-fix the failing tests in my PR"
Troubleshooting
- If the verify tools fail because the environment isn't ready, run
azsdk_verify_setup, report its error, and stop — don't fall back to raw shell build/test commands.
© Azure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .github/skills/azsdk-common-pipeline-fixer of Azure/azure-sdk-tools.
- SKILL.md
- evals/trigger.eval.yaml
Open the folder on GitHubat commit 942ef24
Compare with similar skills
Azsdk Common Pipeline Fixer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Azsdk Common Pipeline Fixer this skillAzure/azure-sdk-tools | 134 | — | ~831 | Automated safety check: Pass | MIT | |
| Azsdk Common Generate SDK LocallyAzure/azure-sdk-for-android | 121 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Update Dependenciesalorence/django-modern-rpc | 111 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Analyze Skill Issuesmicrosoft/GitHub-Copilot-for-Azure | 255 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Shopify AI Toolkit Wrapperjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Python Pypi Package Buildergithub/awesome-copilot | 40k | 1 repos | ~4.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
Update Dependencies
alorence/django-modern-rpc
Routine update of all project dependencies — uv itself, uv.lock (all groups), tool versions pinned in GitHub workflows and .pre-commit-config.yaml (uv, ruff, mypy...), and SHA-pinned GitHub Actions.
- Official
Analyze Skill Issues
microsoft/GitHub-Copilot-for-Azure
Query the integration-test storage account to find why a specific skill's tests are failing.
Shopify AI Toolkit Wrapper
jeremylongshore/tons-of-skills-marketplace
Integrate Shopify's AI Toolkit MCP server with Claude Code for GraphQL validation, Liquid linting, and documentation search.
- Official
Python Pypi Package Builder
github/awesome-copilot
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.
Babysit PR
ZenUml/web-sequence
Monitor and diagnose GitHub Actions checks on ZenUML web-sequence PRs, fixing code-caused CI failures when appropriate.
More from Azure/azure-sdk-tools
All 35 skills in this repo- Official
Apiview Feedback Resolution
Azure/azure-sdk-tools
Analyze and resolve APIView review feedback on Azure SDK PRs.
- Official
Azsdk Common Apiview Feedback Resolution
Azure/azure-sdk-tools
Analyze and resolve APIView review feedback on Azure SDK PRs.
- Official
Azsdk Common Live And Recorded Tests
Azure/azure-sdk-tools
Deploy test resources and run Azure SDK tests in live, record, or playback mode.
- Official
Azsdk Common Pipeline Analysis
Azure/azure-sdk-tools
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format.
- Official
Azsdk Common Prepare Release Plan
Azure/azure-sdk-tools
Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases.
- Official
Azure Typespec Assessment
Azure/azure-sdk-tools
Assess Azure TypeSpec Git diffs for semantic intent, REST and downstream SDK breaking changes, Azure Guidelines compliance, and documentation completeness.
Related
Works with
Categories
Questions about Azsdk Common Pipeline Fixer
What does Azsdk Common Pipeline Fixer do?
Automatically fix Azure SDK CI/CD pipeline failures by applying code changes and verifying locally. Azsdk Common Pipeline Fixer is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Automatically fix Azure SDK CI/CD pipeline failures by applying code changes and verifying locally.
When should I use Azsdk Common Pipeline Fixer?
Azsdk Common Pipeline Fixer fits situations like: : fix pipeline failure; fix failing tests; auto-fix and commit the fix; fix build error.
How do I install Azsdk Common Pipeline Fixer in Claude Code?
Run `npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-fixer -a claude-code`. Or copy the skill folder (.github/skills/azsdk-common-pipeline-fixer in Azure/azure-sdk-tools) into .claude/skills/azsdk-common-pipeline-fixer in your project. Claude Code loads it when a task matches its description.
How do I install Azsdk Common Pipeline Fixer in Codex?
Run `npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-fixer -a codex`. Or copy the skill folder (.github/skills/azsdk-common-pipeline-fixer in Azure/azure-sdk-tools) into .agents/skills/azsdk-common-pipeline-fixer in your project. Codex loads it when a task matches its description.
Can I use Azsdk Common Pipeline Fixer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-fixer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azsdk-common-pipeline-fixer, .gemini/skills/azsdk-common-pipeline-fixer, .github/skills/azsdk-common-pipeline-fixer and .opencode/skills/azsdk-common-pipeline-fixer in your project.
What does Azsdk Common Pipeline Fixer need to run?
SKILL.md names no scripts, command-line tools or credentials: Azsdk Common Pipeline Fixer is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools.
Does Azsdk Common Pipeline Fixer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Azsdk Common Pipeline Fixer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Azsdk Common Pipeline Fixer use?
Azsdk Common Pipeline Fixer is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Azsdk Common Pipeline Fixer use?
About 831 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Azsdk Common Pipeline Fixer?
Skills that share tags, products or a category with Azsdk Common Pipeline Fixer: Azsdk Common Generate SDK Locally (Azure/azure-sdk-for-android, 121 stars), Update Dependencies (alorence/django-modern-rpc, 111 stars), Analyze Skill Issues (microsoft/GitHub-Copilot-for-Azure, 255 stars) and Shopify AI Toolkit Wrapper (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Azsdk Common Pipeline Fixer?
Azure (a GitHub organization, an official publisher) maintains it in Azure/azure-sdk-tools, which has 134 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 10, 2026.
Source: Azure/azure-sdk-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.