ワンクリックでManusで任意のスキルを実行

azsdk-common-pipeline-fixer

スター33

フォーク24

更新日2026年7月17日 19:29

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

azure-sdk

azure-sdk/azure-sdk-for-net

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

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

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-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 environment isn't ready, run azsdk_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.

このリポジトリの他の Skills

同じリポジトリ

azsdk-common-apiview-feedback-resolution

azure-sdk/azure-sdk-for-net

Analyze and resolve APIView review feedback on Azure SDK PRs. **UTILITY SKILL**. USE FOR: APIView comments, API review feedback, SDK API surface changes. DO NOT USE FOR: general code review, non-APIView feedback. INVOKES: azure-sdk-mcp:azsdk_apiview_get_comments, azure-sdk-mcp:azsdk_customized_code_update, azure-sdk-mcp:azsdk_typespec_delegate_apiview_feedback, azure-sdk-mcp:azsdk_run_typespec_validation, azure-sdk-mcp:azsdk_package_generate_code.

2026-07-1733

azsdk-common-generate-sdk-locally

azure-sdk/azure-sdk-for-net

Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization. WHEN: "generate SDK locally", "build SDK", "run SDK tests", "run CI checks", "validate package", "run checks", "update changelog", "fix SDK build errors", "fix breaking changes", "resolve SDK generation errors", "customize TypeSpec", "rename SDK client", "rename SDK model", "hide operation from SDK", "fix analyzer errors", "resolve customization drift", "create subclient", "update metadata", "update version". DO NOT USE FOR: publishing to package registries, CI pipeline configuration, API design review. INVOKES: azsdk_verify_setup, azsdk_package_generate_code, azsdk_package_build_code, azsdk_package_run_check, azsdk_package_run_tests, azsdk_customized_code_update, azsdk_package_update_changelog_content, azsdk_package_update_metadata, azsdk_package_update_version.

2026-07-1733

azsdk-common-pipeline-analysis

azure-sdk/azure-sdk-for-net

Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdk_analyze_pipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in CI", "analyze pipeline", "debug SDK pipeline". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing, applying code fixes (instead use azsdk-common-pipeline-fixer). INVOKES: azure-sdk-mcp:azsdk_analyze_pipeline, azure-sdk-mcp:azsdk_get_pipeline_llm_artifacts, azure-sdk-mcp:azsdk_get_pr_checks, azure-sdk-mcp:azsdk_get_pipeline_status.

2026-07-1733

azsdk-common-prepare-release-plan

azure-sdk/azure-sdk-for-net

Manage Azure SDK release plans and associated SDK PRs. **UTILITY SKILL**. USE FOR: "prepare a release plan", "plan the next SDK release", "create release plan for my package", "get or update release plan", "update API spec or SDK details in release plan", "abandon release plan", "link SDK PR", "namespace approval", "check release plan status". DO NOT USE FOR: SDK generation, pipeline troubleshooting, API review. INVOKES: azure-sdk-mcp:azsdk_create_release_plan, azure-sdk-mcp:azsdk_get_release_plan, azure-sdk-mcp:azsdk_get_release_plan_for_spec_pr, azure-sdk-mcp:azsdk_update_release_plan, azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan, azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan, azure-sdk-mcp:azsdk_abandon_release_plan, azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan, azure-sdk-mcp:azsdk_link_namespace_approval_issue.

2026-07-1733

azsdk-common-sdk-release

azure-sdk/azure-sdk-for-net

Check release readiness and trigger the release pipeline for Azure SDK packages. **UTILITY SKILL**. USE FOR: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK", "release checklist", "release process", "publish a new SDK version", "how to release/publish an SDK". DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation. INVOKES: azure-sdk-mcp:azsdk_release_sdk.

2026-07-1733

mpg-migration-pr-review

azure-sdk/azure-sdk-for-net

Review Azure SDK management-plane migration PRs (Swagger/AutoRest -> TypeSpec). Checks customization quality, TypeSpec decorator usage, and migration-specific anti-patterns on top of the standard mgmt PR review.

2026-06-2433

name	azsdk-common-pipeline-fixer
license	MIT
metadata	{"version":"1.0.0","distribution":"shared"}
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

Pipeline Fixer

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

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-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 environment isn't ready, run azsdk_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.