Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    azure devops workflow

    1

    Triage Azure Boards, review Repos pull requests, and diagnose Pipelines build failures directly from your agent.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    azure devops workflow

    azure devops workflow

    Example session with this skill installed

    Check the latest failed run for the 'ci-workflow' pipeline in project 'Apollo' and tell me why it failed.

    • Read your context and instructions
    • Compiled the azure devops workflow

    I have retrieved the timeline and logs for the most recent failed run of the

    ci-workflow pipeline in the

    Apollo project.

    Pipeline Run Diagnosis: Run #20240512.4

    AttributeDetail
    Pipelineci-workflow
    Run ID88422
    StatusFailed
    Branchmain
    Failing Stepnpm test (Unit Tests)
    Error Code1
    LinkView Run 88422

    Log Excerpt (Step: Unit Tests)

    > apollo-app@1.0.0 test
    > jest
    
    FAIL src/services/auth.service.spec.ts
      ● AuthService › should validate JWT expiration
        expect(received).toBe(expected) // Object.is equality
    
        Expected: true
        Received: false
    
          14 |     const isValid = service.checkToken(expiredToken);
        > 15 |     expect(isValid).toBe(true);
    

    Analysis

    The failure occurred during the unit testing phase. Specifically, the AuthService test suite failed because it expected checkToken to return true for a specific JWT scenario but received false. This indicates a potential regression in the token validation logic or an issue with the test mock data timing.

    Next steps

    1. Inspect src/services/auth.service.ts to verify the JWT expiration logic.
    2. Run the specific test locally using npm test src/services/auth.service.spec.ts.
    3. Check if recent changes to the auth library updated the default expiration behavior.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Context-switching between Azure DevOps portals is a major productivity sink for developers. This skill bridges the gap by providing direct access to Azure Boards, Repos, and Pipelines through your AI agent.

    What it does

    • Triage work items Fetch work item details, summarize state, and manage assignment or acceptance criteria.
    • Review pull requests Inspect diffs, source/target revisions, and policy status for Azure Repos.
    • Diagnose pipeline failures Extract run timelines and step logs to identify root causes in Azure Pipelines.
    • Manage backlogs Resolve team iterations to query and summarize sprint progress.
    • Execute remote actions Update work item fields and post PR comments based on specific user authorization.

    How it works

    1. Context Resolution The agent identifies the organization, project, and repository from links or text.
    2. Resource Inspection It queries the Azure DevOps MCP tools to fetch the current state of work items, diffs, or logs.
    3. Analysis and Drafting It provides summaries, highlights blockers, or drafts review comments for approval.
    4. Targeted Updates Upon explicit instruction, it executes writes back to the Azure DevOps environment.

    Frameworks & tools

    This skill requires the Azure DevOps MCP server configured with your organization credentials. It interacts with Azure Boards, Azure Repos, and Azure Pipelines via standard API toolsets.

    Why this beats prompting it yourself

    Generic prompts cannot access live build logs or private repository diffs. This skill handles the ambiguity of PR numbers and pipeline names by resolving project context and validating state before attempting any write operations.

    Use cases

    • Debug a failing pipeline run by analyzing specific step log excerpts.
    • Summarize a work item's acceptance criteria and blockers for a standup.
    • Perform a technical review of a PR diff and prepare a list of draft comments.
    • Update the status and assignment of multiple work items in a sprint backlog.

    Known limitations

    Requires pre-configured Azure DevOps MCP tools. Limited to the server's configured organization. Write actions require explicit user confirmation. Log analysis excludes sensitive values.

    Requires MCP tool installation. Limited to the server's configured organization. PR reviews depend on diff availability. Log analysis omits credentials and sensitive values.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 10 days ago

    Permissions

    Network Access
    Listed10 days ago

    What's inside

    Frequently Asked Questions

    This skill allows you to triage work items, review pull request diffs, and diagnose CI/CD pipeline failures through your agent, eliminating the need to manually switch between multiple Azure DevOps web portals.

    You will need an active Azure DevOps organization and a configured MCP (Model Context Protocol) server with your credentials to allow the agent to securely access your Boards, Repos, and Pipelines.

    Yes, the skill includes the ability to post comments on pull requests and update work item fields, though these write actions always require your explicit approval for security.

    This skill is compatible with any AI agent or platform that supports the Model Context Protocol (MCP) and has access to the Azure DevOps toolset.

    Unlike static prompts, this skill uses live tool access to fetch real-time data from your private repositories and build logs, ensuring the agent's analysis is based on current state rather than outdated context.

    Log analysis focuses on identifying root causes of build failures, but for security, the skill is designed to exclude sensitive values and secrets from the log excerpts it processes.

    New in APIs & Backend