What is gh-ci-debugging?

A debugging workflow for GitHub Actions failures in the CADT project. GitHub Actions is GitHub's system for running automated builds and tests.

Use it to inspect a failed run, read job and CADT logs, build an error timeline, check wallet state, and review the failing operation's error handling.

It looks beyond a test's visible error by checking server logs, timing, transient failures, source code, and retry handling before blaming infrastructure.

gh-ci-debugging — Skill for Cursor by Chia-Network: A debugging workflow for GitHub Actions failures in the…

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 skills/chia-network/cadt/gh-ci-debugging

Any agent

npx skills add Chia-Network/cadt --skill gh-ci-debugging

Clone the repo

git clone --depth 1 https://github.com/Chia-Network/cadt

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/chia-network/cadt/gh-ci-debugging.svg)](https://agentmods.dev/skills/chia-network/cadt/gh-ci-debugging)

Your own site

<a href="https://agentmods.dev/skills/chia-network/cadt/gh-ci-debugging"><img src="https://agentmods.dev/badge/skills/chia-network/cadt/gh-ci-debugging.svg" alt="Measured on agentmods" height="20"></a>

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,463 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.1	$0.00055	$0.02463
Opus 5	$0.00028	$0.01231
Sonnet 5	$0.00011	$0.00493
Haiku 4.5	$0.00006	$0.00246

Measured yesterday against content hash b8b97c345dc6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

gh-ci-debugging 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 yesterday.

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.

.cursor/skills/gh-ci-debugging/SKILL.md · 201 lines

How it starts

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

Debugging CADT CI with `gh`

Required: Deep investigation before reporting

Do NOT conclude "infrastructure flakiness" or recommend "re-run" without completing ALL of these:

Read CADT server logs, not just test output. Test output shows symptoms (timeouts, assertion failures). CADT logs show causes (process failures, wallet errors, store creation errors). Always run:
```
gh run view --log --job <JOB_ID> 2>&1 | grep "Show CADT logs after" -A 5000 | grep -iE "error|failed|removing"
```
Build a timeline. Extract timestamps for: when the operation started, when errors occurred, when the test gave up. If the error happened early but the test ran for 20+ more minutes, the test couldn't detect the failure — that's a bug, not flakiness.
Check if transient errors recovered. If you see wallet sync errors, check the end-of-job wallet status (Show wallet balance step). If the wallet is synced at job end but the operation failed mid-job, the error was transient and the code should have retried.
Read the source code for the failing operation. Check whether it has retry logic, waitForSpendableCoins() calls, or error handling for transient wallet errors. Compare to similar operations that DO work (e.g., createV2Organization vs upgradeFromV1).
Never recommend "re-run" as the primary action. If investigation reveals a code-level gap (missing retry, missing wallet check, broken fast-fail logic), that's a bug to fix — not flakiness to retry past.

CI Jobs Overview

The .github/workflows/tests.yaml workflow has 5 parallel jobs:

Job name	Job key	What it tests	npm script(s)
v1 integration tests	`test-v1`	Unit/integration (simulator)	`npm run test:v1`
v2 integration tests	`test-v2`	Unit/integration (simulator)	`npm run test:v2`
v2 live api tests	`test-v2-live-api`	E2E with real Chia + datalayer	See below
v1 live api tests	`test-v1-live-api`	E2E with real Chia + datalayer	See below
v1 to v2 upgrade test	`test-v1-to-v2-upgrade`	V1 org creation then upgrade to V2	`npm run test:v1:live:organization:upgrade`

Read the full file on GitHub · 201 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.

yesterday First seen · 201 lines · 55 tokens per session scan A b8b97c345dc6

Subscribe to this mod's changes

gh-ci-debugging is a skill published in the GitHub repository Chia-Network/cadt (41 stars, last pushed 2d ago), licensed Apache-2.0. It adds 55 tokens to every session and 2,463 once invoked, about $0.0003 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-09-04.

CI and CD Debugging DevOps and cloud chia-blockchain

Verification & Quality Assurance

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

ruvnet/RuView · 36 tokens

smoke-test

Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…

garrytan/gbrain · 79 tokens

azdo-build-investigator

Investigate CI failures for dotnet/maui PRs and the nightly/official signed build — build errors, Helix test logs, and binlog analysis. Use when asked about failing checks, CI status, test failures, 'why is CI red', 'build failed', 'what's failing on PR', 'is this PR ready to merge', Helix failures, device test…

dotnet/maui · 115 tokens

fix-ci

Check CI status, analyze test failures, auto-fix obvious issues or discuss with user.

questdb/questdb · 20 tokens

ci-fix

Common safety and triage protocol for .NET MAUI CI-fixer workflows. Use whenever investigating, creating, or advancing a [ci-fix] or [ci-fix-net11] pull request from a ci-scan issue, including frozen ownership snapshots, Continue/Watch/Stop/Skip classification, manual single-issue dispatches, and scheduled sweeps.

dotnet/maui · 81 tokens

mcore-create-issue

Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.

NVIDIA/skills · 26 tokens