get-latest-ci

Fetch the latest CI pipeline status for the current Git branch.

27|7|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/nrwl/nx-ai-agents-config --skill get-latest-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: get-latest-ci
Source: https://github.com/nrwl/nx-ai-agents-config/tree/main/artifacts/skills/get-latest-ci
Command: npx skills add https://github.com/nrwl/nx-ai-agents-config --skill get-latest-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides immediate visibility into the status of the latest CI pipeline execution for the current branch, helping you quickly understand build outcomes and potential issues.

Core Features & Use Cases

  • CI Status Retrieval: Fetches the most recent CI pipeline execution details (status, URL, commit).
  • Failure Analysis: Identifies failed CI runs and checks for available self-healing fixes.
  • Use Case: Before pushing new code, you can use this Skill to ensure the latest CI run for your branch has passed, or to quickly see if a recent failure has a self-healing solution available.

Quick Start

Fetch the latest CI pipeline execution for the current branch.

Frequently Asked Questions about get-latest-ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the latest CI pipeline status for my current Git branch?

You can check the latest CI pipeline status by retrieving the most recent execution details for your current Git branch, which includes the pipeline status, URL, and commit SHA to show build outcomes instantly.

How does CI self-healing work when a pipeline run fails?

CI self-healing identifies failed tasks within a pipeline execution and checks for available suggested fixes, allowing you to see if a recent failure has an automated solution ready to apply.

Can I retrieve CI execution details and failed task fixes using Nx Cloud?

Yes, retrieving CI execution details verifies the Nx Cloud connection and delegates information retrieval via the MCP tool, returning the CIPE status, URL, commit SHA, and any self-healing fixes for failed tasks.

What is the best way to monitor pipeline status before pushing new code?

The best way to monitor pipeline status is to fetch the latest CI execution details for your branch before pushing new code, ensuring the most recent run has passed or identifying any existing failures.

What CI information do I need to diagnose a failed pipeline execution?

To diagnose a failed pipeline execution, you need the CIPE status, URL, commit SHA, and self-healing status, which collectively identify the failed tasks and provide suggested fixes when available.