agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/azure-sdk-tools/.github/skills/azsdk-common-pipeline-fixer/SKILL.md

azsdk-common-pipeline-fixer

Skill135 starsChanged 2 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify ONLY via the azsdk MCP package tools (build → check → tests).

    line 20
  2. Distinctive:

    Never fix infrastructure failures (timeouts, crashes, throttling) — recommend retry.

    line 21
  3. Distinctive:

    Fix: - Read the failing code at the cited lines and apply the minimal fix.

    line 39
  4. Very specific:

    Verify: - Run azsdk_package_build_code → azsdk_package_run_check → azsdk_package_run_tests on the package.

    line 40
  5. Very specific:

    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 …

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-mcp server 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

ToolPurpose
azure-sdk-mcp:azsdk_verify_setupVerify local environment is ready
azure-sdk-mcp:azsdk_package_build_codeBuild the package locally
azure-sdk-mcp:azsdk_package_run_checkRun validation/lint/typecheck locally
azure-sdk-mcp:azsdk_package_run_testsRun tests locally

Prerequisites: azure-sdk-mcp server required. Local clone of the affected SDK language repo. Language build tools installed.

Steps

  1. Find analysis - Reuse an existing analysis from the PR comments; if none, view the azsdk-common-pipeline-analysis skill.
  2. Classify - Fixable (test, type, lint, import, assertion errors) vs retry (infrastructure) vs escalate (breaking API, credentials).
  3. Locate - Identify the affected package, its path, and the files/lines to change.
  4. Fix - Read the failing code at the cited lines and apply the minimal fix.
  5. Verify - Run azsdk_package_build_code → azsdk_package_run_check → azsdk_package_run_tests on the package; all must pass. If the environment isn't ready, run azsdk_verify_setup. Never substitute raw shell build/test commands.
  6. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free