ci-audit

Audits GitHub Actions workflow runs and proposes fixes for CI failures and warnings.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ajbarea/techne --skill ci-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-audit
Source: https://github.com/ajbarea/techne/tree/main/plugins/techne/skills/ci-audit
Command: npx skills add https://github.com/ajbarea/techne --skill ci-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies why your GitHub Actions runs fail or get noisy, then helps you apply repo-side fixes so CI is actionable instead of chaotic.

Core Features & Use Cases

  • PR/run log triage: Pulls the latest Actions run for the current branch/PR and classifies warnings, errors, failures, and deprecation notices.
  • Actionable classification & fixes: Separates items into FIX/BUMP/PROPOSE/DEFER/EXPECTED buckets, then performs in-repo edits for anything fixable.
  • Guardrails for non-blocking failures: Detects continue-on-error cases where errors were emitted but the step still passed, and flags them correctly.
  • Output designed for review: Produces a structured verdict that tells the developer what changed and what still needs human input.

Quick Start

Run the ci-audit skill to review the latest GitHub Actions run for your current branch and fix any repo-side workflow or configuration issues.

Frequently Asked Questions about ci-audit

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

FAQPage Schema
How do I diagnose and fix failing GitHub Actions workflow runs on my pull request?▼

Auditing GitHub Actions involves pulling the latest run logs for your branch or PR, classifying warnings and failures into actionable buckets like FIX or DEFER, and editing in-repo workflow or config files to resolve repo-side issues directly.

What is the best way to handle noisy GitHub Actions runs that pass with warnings?▼

Taming noisy GitHub Actions runs requires classifying warnings and deprecation noise into FIX, BUMP, PROPOSE, DEFER, or EXPECTED buckets, then performing in-repo edits to workflow or config files to eliminate the chaos.

Can I triage external PR checks like Codecov or GitGuardian when auditing GitHub Actions?▼

Yes, auditing GitHub Actions includes external PR checks like Codecov and GitGuardian, pulling logs to classify their failures and warnings, and generating a structured verdict that separates fixable in-repo issues from those needing human input.

Does this CI audit approach detect errors hidden by continue-on-error in GitHub Actions workflows?▼

Yes, the CI audit detects GitHub Actions continue-on-error cases where errors were emitted but the step still passed, flagging these non-blocking failures correctly so hidden issues are addressed during workflow triage.

Do I need the gh CLI to locate workflow runs for GitHub Actions log analysis?▼

Yes, GitHub Actions log analysis requires using the gh CLI to locate the latest run per workflow on the current branch or PR, pull logs for classification, and edit only in-repo workflow, config, source, or test files to apply fixes.

What limitations exist when fixing GitHub Actions deprecation notices through a CI audit?▼

Fixing GitHub Actions deprecation notices is limited to editing only in-repo workflow, config, source, or test files; external service configurations or account-level GitHub settings cannot be modified and are classified as PROPOSE or DEFER for human review.