What is fixing-github-actions-builds?

A procedure for diagnosing and fixing failed GitHub Actions builds. GitHub Actions is GitHub's service for automatically running tasks such as tests and deployments.

Use it to list recent runs, inspect failed logs with the GitHub CLI, reproduce errors locally, apply fixes, and test them.

It turns a failed workflow into a repeatable investigation, from reading logs through reproducing and verifying the fix.

fixing-github-actions-builds — Cursor rule by TechNickAI

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add rules/technickai/claude_telemetry/fixing-github-actions-builds

Clone the repo

git clone --depth 1 https://github.com/TechNickAI/claude_telemetry

Made for: Cursor.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 565 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00007	$0.00565
Opus 5	$0.00003	$0.00282
Sonnet 5	$0.00001	$0.00113
Haiku 4.5	$0.00001	$0.00056

Measured 2d ago against content hash 2970860ea1c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fixing-github-actions-builds scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

fixing-github-actions-builds — 92% identical, 1 lines differ

.cursor/rules/fixing-github-actions-builds.mdc · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fixing Broken GitHub Actions Builds

Purpose

This guide documents the process for diagnosing and fixing broken GitHub Actions builds using the gh CLI.

Prerequisites

Check if gh is installed

First, verify the GitHub CLI is installed:

gh --version

If gh is not installed

Politely stop and guide the developer:

The GitHub CLI (gh) is not installed. Let's get that set up first!

Installation (macOS):
brew install gh
gh auth login
Follow the prompts to authenticate with GitHub. Once complete, we can proceed with debugging the build!

Diagnostic Workflow

Step 1: List Recent Workflow Runs

gh run list --limit 5

Identify the failed run (marked with X or failure status). Note the run ID.

Step 2: Get Failed Logs

gh run view <run-id> --log-failed | cat

This shows ONLY the logs from failed steps. Analyze these logs to identify the root cause.

Step 3: Reproduce Locally

Based on the error in the logs, reproduce the failure locally to verify the fix.

Step 4: Make the Fix

Edit the relevant files to fix the issue identified in the logs.

Step 5: Verify Locally

Test the fix thoroughly to ensure it resolves the issue.

Step 6: Report to Developer

DO NOT commit or push changes!

Report to the developer:

Build issue fixed!

Changes made:

path/to/file: Description of change

Next steps:

Review the changes with git status and git diff

Test locally if desired

Commit and push when ready

Monitor the new build with gh run watch

Integration with Cursor

When a developer says "the build is broken" or "fix the GitHub Actions build":

Run gh --version to verify installation (stop if not installed)
Run gh run list --limit 5 to see recent runs
Identify the failed run ID
Run gh run view <run-id> --log-failed | cat to get error details
Analyze the logs and identify root cause
Fix the issue locally
Verify the fix works
Report back to developer with changes and next steps

Read the full file on GitHub · 103 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 103 lines · 7 tokens per session scan A 2970860ea1c4

Subscribe to this mod's changes

fixing-github-actions-builds is a cursor rule published in the GitHub repository TechNickAI/claude_telemetry (30 stars, last pushed 10mo ago), licensed MIT. It adds 7 tokens to every session and 565 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Data and AI Debugging Testing anthropic-claude claude-code cli datadog honeycomb llm-monitoring

fixing-github-actions-builds