Identify and attribute GitHub Actions failures to specific owners or workflows to optimize CI stability and reduce wasted minutes.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install github-actions-failure-owner-audit
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install github-actions-failure-owner-audit using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is GitHub Actions Failure Owner Audit?
The GitHub Actions Failure Owner Audit is a powerful diagnostic tool within the Openclaw Skills library designed to provide deep visibility into CI instability. By analyzing GitHub Actions run exports, this skill maps failed conclusions—such as timeouts, cancellations, and startup failures—to the specific actors or workflows responsible. It empowers engineering leaders and DevOps teams to stop guessing and start routing stabilization efforts based on quantifiable data, specifically failed run counts and total wasted runtime minutes.
This utility is particularly effective for large-scale monorepos or organizations with hundreds of active workflows where identifying the root cause of CI noise can be difficult. By leveraging the Openclaw Skills framework, developers can automate the detection of hotspots and ensure that the most impactful failures are addressed first, improving overall development velocity.
GitHub Actions Failure Owner Audit Use Cases
- Identifying the most noisy workflows in a large organization to prioritize refactoring.
- Attributing CI costs and wasted minutes to specific teams or individual developers.
- Monitoring release branch stability by filtering for specific branch patterns during critical deployment windows.
- Automating alerts within CI/CD pipelines when failure thresholds are exceeded for critical owners.
- Mapping automated bot accounts like Dependabot or Renovate to specific ownership categories for cleaner reporting.
How GitHub Actions Failure Owner Audit Works
- The skill ingests one or more GitHub Actions run JSON files, typically exported using the GitHub CLI paginate command.
- It filters the imported runs to focus exclusively on failure-like conclusions such as failure, cancelled, timed_out, or startup_failure.
- Data is grouped according to user-defined logic, such as by repository, actor, or a combination of actor and workflow.
- The script calculates scoring metrics for each group, identifying hotspots based on the frequency of failures and the cumulative duration of wasted runtime.
- A final report is generated in either human-readable text or machine-parseable JSON format, allowing for manual triage or integration into custom dashboards.
GitHub Actions Failure Owner Audit Setup
To begin using this skill from the Openclaw Skills repository, ensure you have bash and python3 installed in your environment. First, export your GitHub Actions run data using the GitHub CLI:
gh api repos/<owner>/<repo>/actions/runs --paginate > artifacts/github-actions-runs/<owner>-<repo>.json
Then, execute the audit script with your desired configuration parameters:
RUN_GLOB='artifacts/github-actions-runs/*.json' \
bash skills/github-actions-failure-owner-audit/scripts/failure-owner-audit.sh
GitHub Actions Failure Owner Audit Data Schema & Taxonomy
The skill processes standard GitHub API run objects and organizes data into an actionable taxonomy. The output captures the following dimensions:
| Metric | Description |
|---|---|
| actor | The user or bot account that triggered the workflow run. |
| repository | The source repository where the failure occurred. |
| workflow | The specific GitHub Actions workflow filename or ID. |
| conclusion | The specific failure state (e.g., failure, cancelled, timed_out). |
| minutes | The total duration in minutes for the failed execution. |
If an optional OWNER_MAP_FILE is provided, the skill uses a JSON mapping of regex patterns to aggregate individual actors into team-based ownership groups.
GitHub Actions Failure Owner Audit Advanced Features
- Customizable failure thresholds that trigger different status levels (Warn vs. Critical) based on run counts or minutes.
- Comprehensive regex filtering support to include or exclude specific repositories, branches, actors, and workflows.
- Exit code management for CI/CD integration, allowing the script to fail a build if critical ownership hotspots are detected.
- Advanced ownership mapping via external JSON files to translate developer handles into organizational teams.
- Support for granular grouping modes like owner-workflow to see exactly which teams are breaking specific pipelines within the Openclaw Skills ecosystem.
SKILL.md
Loading
Related Openclaw Skills
GitHub Actions Failure Matrix
Summarize and rank GitHub Actions matrix job failures across multiple runs to quickly identify unstable OS or runtime combinations.
GitHub Actions Failure Hour Audit
A diagnostic tool that analyzes GitHub Actions run history to identify specific days and hours when workflow failures cluster.
GitHub Actions Duplicate Run Audit
A specialized utility for identifying redundant GitHub Actions executions and quantifying wasted CI/CD resources.
GitHub Actions Deploy Risk Audit
A DevOps tool that analyzes GitHub Actions history to identify and score risky deployment workflows before production releases.
GitHub Actions Failure Phase Audit
A diagnostic tool that categorizes GitHub Actions failures into phases like build, test, and deploy to rank hotspots by time impact.
GitHub Actions Failure Spike Audit
A specialized tool to detect workflow performance degradation by comparing recent failure rates against historical baselines.
METADATA
Featured*
