github-ci-failure-triage skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.
github-ci-failure-triage is agent-read markdown (skill) from yeaight7/agent-powerups: Use when a GitHub PR shows failing checks and a clean failure readout is needed before changing any code..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## Purpose Produce a clean, GitHub-native readout of failing PR checks before any code is edited. Triage first: summarize the breakage and propose a local fix plan; implement only after approval when the task is framed as triage-first. ## When to Use - A PR is red and the cause is unknown - The user asks why CI is failing before asking for a fix - A triage-first readout must precede any code edits ## Inputs - The PR number or URL (or the current branch to resolve it from) - `gh` CLI authenticated for the repository, or a GitHub connector ## Core Rules - Resolve the PR first - Inspect failing checks before guessing - Prefer GitHub-native data (`gh` or a GitHub connector) over screenshots or copied snippets - Summarize the failure before proposing code changes - Implement only after approval when the task is framed as triage-first - Do not auto-commit, auto-push, or auto-rerun remote writes without approval ## Workflow 1. **Resolve the PR:** ```bash gh pr view <number-or-url> --json number,title,headRefName,url gh pr view --json number,title,headRefName,url # from the current branch ``` …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/github-ci-failure-triage@git:20260606.07e774dmdr add yeaight7/agent-powerups/github-ci-failure-triage@sha256:1131e16b586477b8Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_vsetfctfk27f3y53)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.07e774d latest | 2026-06-06 | 07e774d | 3,239 B | A | view · diff |
| git:20260512.7743d32 | 2026-05-12 | 7743d32 | 1,561 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3239 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vsetfctfk27f3y53 GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/github-ci-failure-triage GET https://markdownregistry.com/api/v1/blob/1131e16b586477b82d6a716f2e6fa01c23bde25d6d49ca75998caf3eb38cf6ad
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from yeaight7/agent-powerups
Every file in yeaight7/agent-powerups