fetch-failed-pr-checks SKILL.md skillA
fetch-failed-pr-checks from motleyai/living-architecture is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add motleyai/living-architecture/fetch-failed-pr-checks@git:20261109.1aa4181Pins git:20261109.1aa4181 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- motleyai/living-architecture
- Path
plugin/skills/fetch-failed-pr-checks/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261109.1aa4181, committed Nov 9, 2026
- First version recorded
- Sep 27, 2026
- Size
- 3,708 bytes
- Repository stars
- 14
- License
- MIT
Use when the user asks to check / fetch / list / show failed CI checks (GitHub Actions, external CI) on a GitHub PR — including details/logs of the failures. Pulls the statusCheckRollup, filters to non-passing terminal states, and (for GitHub Actions runs) appends a log excerpt, or why there is none.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
**Preflight:** run `la-doctor --plugin <this skill's base directory>` once per session before using any `la-*` or `dr-*` command; if it fails, stop and show the user its output.
# Fetch failed CI checks (and their log excerpts) for a PR
## How to run
```bash
la-fetch-failed-pr-checks <PR_NUMBER> [--repo OWNER/REPO] [--max-log-lines N]
```
- `<PR_NUMBER>` — required.
- `--repo OWNER/REPO` — optional; defaults to the cwd repo via `gh repo view`.
- `--max-log-lines N` — cap each failed job's log excerpt at N lines (default 200). Pass `0` to skip log fetching entirely.
## Output
Always emits **both**:
- **Markdown to stdout** — one section per failed check: workflow / job name, conclusion, details URL, and either a log excerpt inside a collapsible `<details>` block whose summary names its source, or a line saying why there is none.
- **JSON file** at `${TMPDIR:-/tmp}/failed-pr-checks-<pr>-<utc-ts>.json`. Path printed on the last line, prefixed `JSON: `. Schema:
```json
{
"pr": 70,
"repo": "owner/name",
"failed_checks": [
{
"typename": "CheckRun" | "StatusContext" | "WorkflowRun",
"name": "test",
"workflow_name": "CI",
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7xblludl7jya3dfr/114401e085111fe041258f74ba3d26e83d0476a24befc2650b567ba7484d076c.json
Then /plugin install fetch-failed-pr-checks@markdownregistry-7xblludl7jya3dfr in Claude Code. It installs git:20261109.1aa4181, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add motleyai/living-architecture/fetch-failed-pr-checks@sha256:114401e085111fe0The line at the top of this page pins the label git:20261109.1aa4181, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7xblludl7jya3dfr)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in motleyai/living-architecture/fetch-failed-pr-checks since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of fetch-failed-pr-checks from somewhere else? Ask it: where did my fetch-failed-pr-checks come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Sep 27, 2026 and Nov 9, 2026, about one every 11 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261109.1aa4181 latest | 2026-11-09 | 1aa4181 | 3,708 B | A | view · diff |
| git:20261109.e8e5083 | 2026-11-09 | e8e5083 | 3,705 B | A | view · diff |
| git:20261005.1d349d3 | 2026-10-05 | 1d349d3 | 3,241 B | A | view · diff |
| git:20261001.eb09810 | 2026-10-01 | eb09810 | 3,217 B | A | view · diff |
| git:20260927.7349664 | 2026-09-27 | 7349664 | 3,217 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/fetch-failed-pr-checks/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (3708 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
motleyai/living-architecture · 14 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7xblludl7jya3dfr GET https://markdownregistry.com/api/v1/resolve?ref=motleyai/living-architecture/fetch-failed-pr-checks GET https://markdownregistry.com/api/v1/blob/114401e085111fe041258f74ba3d26e83d0476a24befc2650b567ba7484d076c
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.