lane-ci-investigation

Query GitHub PR checks and workflow runs to diagnose the first actionable CI failure.

1|Updated Mar 7, 2026

Search Tags:#workflow #investigation #logs #github #diagnose #ci #pr-checks

Ready to run

npx skills add https://github.com/pweiskircher/pi-lanes --skill lane-ci-investigation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lane-ci-investigation
Source: https://github.com/pweiskircher/pi-lanes/tree/main/skills/lane-ci-investigation
Command: npx skills add https://github.com/pweiskircher/pi-lanes --skill lane-ci-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify CI status for the current lane by querying GitHub PR checks and recent workflow runs, surfacing issues without performing changes.

Core Features & Use Cases

Starts with GitHub checks using gh to locate the relevant PR or run for the current lane.
If issues exist, investigates the first actionable failure and provides a concise human-friendly summary without applying code changes.
Follows lane context and guardrails (including jj detached HEAD scenarios) to deliver a bounded, non-remedial CI diagnosis.

Quick Start

Ask pi to investigate the current lane's CI and report the first actionable failure with a concise summary.

Frequently Asked Questions about lane-ci-investigation

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

FAQPage Schema

How do I diagnose GitHub PR check failures for my current lane?▼

To diagnose GitHub PR check failures, the Skill queries recent workflow runs using gh, identifies the first actionable failure within your lane context, and summarizes the issue without applying code changes.

What is the best way to investigate CI workflow runs without modifying code?▼

Investigating CI workflow runs without modifying code is achieved by enforcing guardrails that prevent automated remediation, ensuring the Skill only surfaces and summarizes the failure for human review.

Does this CI investigation tool work with detached HEAD scenarios?▼

Yes, this CI investigation tool works with detached HEAD scenarios by maintaining awareness of the current lane context, allowing it to accurately locate relevant GitHub PR checks and workflow runs.

Do I need gh installed to summarize GitHub CI failures?▼

Yes, you need gh installed to summarize GitHub CI failures, as the Skill requires access to the GitHub CLI to query PR checks and recent workflow runs for the current lane.

Why does CI investigation stop at the first actionable failure?▼

CI investigation stops at the first actionable failure to provide a concise, human-ready summary of the root cause, avoiding overwhelming output and strictly avoiding any automated code changes.

Can I use this to automatically fix failing GitHub workflow runs?▼

No, you cannot use this to automatically fix failing GitHub workflow runs because the Skill includes guardrails that prevent automated remediation, focusing solely on diagnosis and summarization.