New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Fix PR Checks

by adamayoung in adamayoung/TMDb

Fix the currently-failing status checks on the current branch's PR in one sweep — route each failing check to the right diagnosis skill (via a Haiku subagent, escalating to Opus on a repeat…

Apache-2.0Auto-check passedAgent Workflows

Install Fix PR Checks

skills CLI
$ npx skills add adamayoung/TMDb --skill fix-pr-checks -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install adamayoung/TMDb fix-pr-checks --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/adamayoung/TMDb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/fix-pr-checks .claude/skills/fix-pr-checks && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fix-pr-checks
GitHub stars
178
Token cost
~3k tokens
SKILL.md length
1,121 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
Apache-2.0

At a glance

Fix the currently-failing status checks on the current branch's PR in one sweep — route each failing check to the right diagnosis skill (via a Haiku subagent, escalating to Opus on a repeat…

  • Works in 5 steps: Find the PR → List the checks → Diagnose each failing check (Haiku… → …
  • Tasks that involve Subagents
  • SKILL.md covers It stands on the diagnosis…, Principles, 0. Find the PR and 1. List the checks, plus 4 more sections
  • Calls git; needs TMDB_API_KEY

What it does

Fix PR Checks is an agent skill from adamayoung/TMDb. Fix the currently-failing status checks on the current branch's PR in one sweep — route each failing check to the right diagnosis skill (via a Haiku subagent, escalating to Opus on a repeat failure), apply and verify the fix, commit, and push once — then return a summary. Use standalone when CI is red, or as the check-fixing step invoked by /watch-pr. Repo is adamayoung/TMDb.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Subagents. It works with Model Context Protocol and GitHub. The repository describes itself as: The Movie Database Swift Package. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Subagents

Example prompts

  • “/fix-pr-checks”

Requirements

  • A credential in TMDB_API_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Find the PR
  2. List the checks
  3. Diagnose each failing check (Haiku first, Opus on a repeat)
  4. Apply, verify, commit
  5. Push once, then finish

What it can do on your machine

Read from SKILL.md and the folder at commit a3f1311. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • TMDB_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fix PR Checks loads about 3k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 1,121 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from adamayoung/TMDb at commit a3f1311, republished under its Apache-2.0 licence (© adamayoung). 1,121 words, ~3,035 tokens.

Download SKILL.mdSave it as .claude/skills/fix-pr-checks/SKILL.md (or your agent's skills folder).
name
fix-pr-checks
description
Fix the currently-failing status checks on the current branch's PR in one sweep — route each failing check to the right diagnosis skill (via a Haiku subagent, escalating to Opus on a repeat failure), apply and verify the fix, commit, and push once — then return a summary. Use standalone when CI is red, or as the check-fixing step invoked by /watch-pr. Repo is adamayoung/TMDb.

Fix PR Checks

Get a pull request's failing checks green: for each failing status check, diagnose the cause, apply and verify a fix, and push. This is a single sweep over the checks failing right now — it diagnoses and fixes them, pushes once, and returns. Waiting on pending checks and deciding whether to sweep again belong to the caller (you, or /watch-pr).

Repo is adamayoung/TMDb. GitHub reads use the GitHub MCP (mcp__github__*); gh is authenticated and used for the blocking CI wait. If an MCP call fails with 401/403 (PAT expired or missing scope), fall back to the equivalent gh command.

It stands on the diagnosis skills

Don't read CI logs yourself. The analysis is already a capability — delegate it to a Haiku subagent running the matching diagnosis skill (a repeat failure re-diagnoses on Opus — see §2), so raw logs never enter your context and you get back a file:line cause and a concrete fix:

  • The Integration check (live-API suite from integration.yml) → /diagnose-integration-failure
  • Any CI check — lint, markdown lint, build, or unit tests from ci.yml → /diagnose-ci-failure

This skill is the act-on-it layer: route → fix → verify → commit → push.

Principles

  1. One sweep, then return. Handle every check failing at invocation, push once, report. Don't loop waiting for the re-run — that convergence is the caller's job.
  2. Diagnose via Haiku, escalate a repeat to Opus, fix locally. Get Cause/Fix from the diagnosis skill, then apply it and verify before claiming it fixed with the delegated build/test skills. First diagnosis of a check runs on Haiku; a check that comes back after a fix re-diagnoses on Opus (§2).
  3. Respect the attempt cap. A check gets at most 3 fix→push attempts (tracked in the run ledger). If it still fails on the same root cause, stop touching it and report it exhausted — never loop forever.
  4. Failing only. Act on fail checks. pending checks are not yours to chase — report them and leave waiting to the caller. claude-review and other neutral checks are non-blocking.
  5. Never fake green. Don't edit .github/workflows/* or CI config to silence a check, and don't force-push, without surfacing to the user first.

0. Find the PR

Find the open PR for the current branch with mcp__github__list_pull_requests (owner/repo from the origin remote, head: <owner>:<branch>, state: open), or read a specific one with mcp__github__pull_request_read method get. Take number/html_url/state/head.ref from the result.

  • An explicit PR number in the arguments overrides the current branch.
  • No PR for the current branch → stop and tell the user (suggest /pr).
  • State not open → stop and report.

1. List the checks

Use mcp__github__pull_request_read method get_check_runs (owner/repo from origin, pullNumber: <n>) — the individual CI/CD check runs for the head commit. Classify each by status + conclusion:

  • fix it (below): conclusion is failure / timed_out / cancelled / action_required.
  • pending (report, leave for the caller to wait on): status is not completed (queued / in_progress).
  • ignore: conclusion is success / skipped / neutral (e.g. claude-review).

If nothing is failing, return immediately (note any pending checks).

2. Diagnose each failing check (Haiku first, Opus on a repeat)

For each fail check under its attempt cap, spawn the check-diagnoser agent (Agent tool, subagent_type: check-diagnoser — its no-fix/no-build contract, report shape, and Haiku floor-pin live in .claude/agents/check-diagnoser.md), substituting the check name and the routed skill. Pick the model from the check's ledger history and pass it explicitly (a call-site model beats the agent's frontmatter pin — ADR-0014):

  • First attempt → model: haiku.
  • Repeat (the ledger shows a prior attempt for this check — a fix that didn't verify, or the check failed again after the push) → model: opus, prepending one line of prior-attempt context to the prompt: the previous Cause/Fix and why it didn't stick. A misdiagnosis costs a full fix→push→CI round trip; don't pay it twice on the same model tier.

Registry lag. A freshly merged agent file may not register as a spawnable subagent_type until a new session (knowledge/delivery-retros.md), and an unrecognised type silently starts a plain general-purpose agent — with no contract at all now that the prompt below carries none. If check-diagnoser is not a recognised type, don't fall through silently: say so, and re-spawn as general-purpose with .claude/agents/check-diagnoser.md read into the prompt as its contract.

text
The `<CHECK NAME>` check failed on the TMDb PR for branch `<branch>`.

Use the `<SKILL>` skill to diagnose it.
Show full SKILL.md (434 more words)Show less
Two or more failing checks → one Workflow

One failing check stays a direct Agent call; a Workflow for a single agent is pure overhead. At two or more, fan out instead — one diagnosis agent per check, each schema-validated, with model set per agent from the ledger history so the Haiku→Opus escalation survives (a Workflow cannot see that history on its own — pass it in via args).

Run the script below via the Workflow tool with args: { branch, checks: [{ name, skill, priorAttempt }] } — priorAttempt is the ledger's record for that check (omit on a first attempt). It is embedded here, not a file, because it runs once per invocation — the same rule that keeps /review-plan's and /review-changes's scripts embedded, while deliver-panel.js lives in .claude/workflows/ (it runs at every panel decision point — seven of them — in a single run). Invoking this skill is itself the opt-in to call Workflow.

The guards are executable throws, not instructions: a malformed payload must fail at agent zero, never mid-fan-out.

javascript
export const meta = {
  name: 'fix-pr-checks-diagnose',
  description: 'Diagnose each failing PR check in parallel, one read-only agent per check',
  phases: [{ title: 'Diagnose', detail: 'one agent per failing check' }],
}

// `args` can arrive as a JSON STRING rather than an object (a known harness
// gotcha). Parsing is not optional: iterating a string character-by-character
// once fanned out ~281 agents into a spend limit, so validate the SHAPE before
// spawning anything.
const input = typeof args === 'string' ? JSON.parse(args) : args
if (!input || typeof input !== 'object') {
  throw new Error('fix-pr-checks: args must be an object (or a JSON string encoding one).')
}
if (!Array.isArray(input.checks)) {
  throw new Error(
    `fix-pr-checks: args.checks must be an ARRAY, got ${typeof input.checks}. ` +
      `Refusing to fan out — iterating a non-array here is the ~281-agent failure.`
  )
}
if (!input.checks.length) throw new Error('fix-pr-checks: args.checks is empty — nothing to diagnose.')
// Element shape too, not just the container. `checks: ['CI', 'Integration']` is the
// natural malformed form: it passes an Array.isArray check, then spawns agents whose
// prompts read "the `undefined` check failed" and reports full coverage, because the
// dead-detection compares `undefined === undefined`. A `null` element instead throws
// at the dead-detection — AFTER the agents ran, discarding their work. Both violate
// "fail at agent zero", so validate here.
if (!input.checks.every((c) => c && typeof c === 'object' &&
    typeof c.name === 'string' && c.name && typeof c.skill === 'string' && c.skill)) {
  throw new Error(
    'fix-pr-checks: every entry in args.checks must be an object { name, skill } with ' +
      'non-empty strings. Refusing to fan out on a malformed element.'
  )
}
if (typeof input.branch !== 'string' || !input.branch) {
  throw new Error('fix-pr-checks: args.branch must be a non-empty string.')
}

const DIAGNOSIS_SCHEMA = {
  type: 'object',
  additionalProperties: false,
  properties: {
    check: { type: 'string' },
    summary: { type: 'string', description: 'one or two sentences on what failed' },
    likelyCause: { type: 'string', description: 'the ranked root cause' },
    suggestedFix: { type: 'string', description: 'the concrete next step' },
    fileLine: { type: 'string', description: 'the offending file:line, or "unknown"' },
    observed: {
      type: 'string',
      description:
        'for an Integration check: the live call made and the shape returned, or "unavailable (headless)"; ' +
        'omit for CI checks. NEVER include a URL, command or header carrying TMDB_API_KEY.',
    },
  },
  required: ['check', 'summary', 'likelyCause', 'suggestedFix'],
}

phase('Diagnose')
const results = await parallel(input.checks.map((c) => () =>
  agent(
    `The \`${c.name}\` check failed on the TMDb PR for branch \`${input.branch}\`.\n\n` +
      `Use the \`${c.skill}\` skill to diagnose it.` +
      (c.priorAttempt
        ? `\n\nTHIS IS A REPEAT. The previous attempt did not stick:\n${c.priorAttempt}\n` +
          `Do not re-propose it — find what that diagnosis missed.`
        : ''),
    {
      label: `diagnose:${c.name}`,
      phase: 'Diagnose',
      // The agent definition carries the no-build rule and report contract.
      agentType: 'check-diagnoser',
      // Haiku first; a repeat escalates. The conductor supplies the history —
      // a Workflow cannot see the ledger's per-check attempt counters.
      model: c.priorAttempt ? 'opus' : 'haiku',
      schema: DIAGNOSIS_SCHEMA,
    }
  ).then((r) => r && { ...r, check: c.name })
))

const live = results.filter(Boolean)
const dead = input.checks.filter((c) => !live.some((r) => r.check === c.name)).map((c) => c.name)
if (dead.length) log(`WARNING: no diagnosis returned for ${dead.join(', ')} — treat as undiagnosed, not as clean`)

return { diagnoses: live, undiagnosed: dead }

The fix stays here. Only diagnosis is delegated; §3's apply → verify → commit and §4's single batched push run in the conductor, which owns the build slot and the attempt counters. A check in undiagnosed is not clean — leave it and report it.

3. Apply, verify, commit

From the returned Cause/Fix:

  1. Apply the fix to the offending file:line.
  2. Verify locally with the matching delegated skill — /lint, /build, /test, or /integration-test (they run in Haiku subagents; logs stay out of context).
  3. Commit with a gitmoji message; record the SHA. Batch the sweep's pushes — commit per fix, but git push once after all failing checks are handled (§4), so the re-run covers everything in one CI cycle.
  4. Increment that check's attempt counter in the ledger.

If the diagnosis is ambiguous or the fix is risky, don't guess — leave the check, note it for the user, and move on.

4. Push once, then finish

After all failing checks are handled, if you committed any fixes, git push once (it re-triggers CI — expected). There is no pre-commit hook (.git/hooks/ holds only *.sample), so nothing lints on your behalf — run /lint before committing, or a lint fix can itself land a lint failure.

Return: sweep summary

Report, concisely:

  • Fixed — check name → cause (file:line) → commit SHA.
  • Exhausted — checks at the 3-attempt cap still failing on the same root cause; stop and hand to the user.
  • Skipped/ambiguous — failing checks you intentionally left (risky/unclear), with why.
  • Pending — checks still in progress, left for the caller to wait on.
  • Whether you pushed (and thus re-triggered CI) so the caller can decide whether to sweep again.

Arguments: $ARGUMENTS

© adamayoung, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/fix-pr-checks of adamayoung/TMDb.

Open the folder on GitHubat commit a3f1311

Compare with similar skills

Fix PR Checks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fix PR Checks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix PR Checks this skilladamayoung/TMDb178—~3kAutomated safety check: PassApache-2.0
Akb Ingestdnotitia/akb162—~2kAutomated safety check: PassCustom licence
Load PR CommentsNeoLabHQ/context-engineering-kit1.8k—~2.1kAutomated safety check: PassGPL-3.0
Vibe Kanbanaiskillstore/marketplace433—~4.4kAutomated safety check: NotesNone
Skill Seekers Builderyusufkaraaslan/Skill_Seekers15k—~760Automated safety check: PassMIT
Claude Automation Recommenderanthropics/claude-plugins-official38k3 repos~2.7kAutomated safety check: NotesApache-2.0

Similar skills

  • Akb Ingest

    dnotitia/akb

    Ingest whatever you point at into an AKB vault — a local file, a web URL, a GitHub PR/release/commit, a Confluence page, or a Jira issue.

    162 GitHub stars~2k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Load PR Comments

    NeoLabHQ/context-engineering-kit

    A skill your agent uses to load open/unresolved PR review comments then aggregate them as tasks in .specs/comments/.md for parallel agents to fix.

    1.8k GitHub stars~2.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Vibe Kanban

    aiskillstore/marketplace

    Manage AI coding agents on a visual Kanban board. An agent skill from aiskillstore/marketplace.

    433 GitHub stars~4.4k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes

  • Skill Seekers Builder

    yusufkaraaslan/Skill_Seekers

    Detects the type of a knowledge source and uses the Skill Seekers MCP tools to turn docs, repos, PDFs or videos into packaged AI skills.

    15k GitHub stars~760 tokensUpdated 10 days ago
    Agent WorkflowsAuto-check passed

  • Claude Automation Recommender

    anthropics/claude-plugins-official

    Official

    Scans a codebase and suggests which Claude Code hooks, subagents, skills, plugins and MCP servers fit its stack, without changing any files.

    38k GitHub starsUsed in 3 repos~2.7k tokens
    Agent WorkflowsAuto-check: notes

  • CC Workflow Studio AI Editor

    breaking-brake/cc-wf-studio

    Creates and edits visual agent workflows in CC Workflow Studio through conversation, with the agent reading and writing the canvas over MCP.

    5.4k GitHub stars~561 tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed

More from adamayoung/TMDb

All 18 skills in this repo

  • Swift DocC Documentation

    adamayoung/TMDb

    Writes and maintains DocC /// comments for the public API of the TMDb Swift package, following the project's summary patterns and comment structure.

    178 GitHub stars~2.6k tokensUpdated 7 days ago
    Auto-check passed

  • TMDb Integration Failure Fixer

    adamayoung/TMDb

    Diagnoses a failing scheduled TMDb Integration run, re-runs transient failures, and fixes real API drift on its own branch with a PR, merging it only when told to.

    178 GitHub stars~2.7k tokensUpdated 7 days ago
    Auto-check passed

  • Implement Plan (Canon TDD)

    adamayoung/TMDb

    Drives an approved plan to completion test-first, deriving a Canon TDD test list, showing it before any code and stopping only when every item is written, passing and green.

    178 GitHub stars~4.5k tokensUpdated 7 days ago
    Auto-check passed

  • TMDb Backlog Triager

    adamayoung/TMDb

    Grooms the Backlog column of a GitHub project board by re-verifying each issue against current main, closing dead ones, promoting actionable ones to Ready and naming the decision the rest need.

    178 GitHub stars~5k tokensUpdated 7 days ago
    Auto-check passed

  • Canon TDD Workflow

    adamayoung/TMDb

    Has your agent build features and fix bugs in Canon TDD order: write a test list, then one failing test, make it pass, refactor, and repeat until the list is empty.

    178 GitHub stars~1.3k tokensUpdated 7 days ago
    Auto-check passed

  • Capture Knowledge

    adamayoung/TMDb

    Records non-obvious lessons from a finished task, such as gotchas, API quirks and design decisions, into a project's knowledge folder before a pull request opens.

    178 GitHub stars~2.3k tokensUpdated 7 days ago
    Auto-check passed

Works with

Categories

Questions about Fix PR Checks

What does Fix PR Checks do?

Fix the currently-failing status checks on the current branch's PR in one sweep — route each failing check to the right diagnosis skill (via a Haiku subagent, escalating to Opus on a repeat…. Fix PR Checks is an agent skill from adamayoung/TMDb. Fix the currently-failing status checks on the current branch's PR in one sweep — route each failing check to the right diagnosis skill (via a Haiku subagent, escalating to Opus on a repeat failure), apply and verify the fix, commit, and push once — then return a summary.

When should I use Fix PR Checks?

Fix PR Checks fits situations like: tasks that involve Subagents.

How do I install Fix PR Checks in Claude Code?

Run `npx skills add adamayoung/TMDb --skill fix-pr-checks -a claude-code`. Or copy the skill folder (.claude/skills/fix-pr-checks in adamayoung/TMDb) into .claude/skills/fix-pr-checks in your project. Claude Code loads it when a task matches its description.

How do I install Fix PR Checks in Codex?

Run `npx skills add adamayoung/TMDb --skill fix-pr-checks -a codex`. Or copy the skill folder (.claude/skills/fix-pr-checks in adamayoung/TMDb) into .agents/skills/fix-pr-checks in your project. Codex loads it when a task matches its description.

Can I use Fix PR Checks in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add adamayoung/TMDb --skill fix-pr-checks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-pr-checks, .gemini/skills/fix-pr-checks, .github/skills/fix-pr-checks and .opencode/skills/fix-pr-checks in your project.

What does Fix PR Checks need to run?

Going by SKILL.md and its folder, Fix PR Checks needs the command-line tools its instructions call (git) and credentials named TMDB_API_KEY. Our summary lists: A credential in TMDB_API_KEY.

Does Fix PR Checks access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Fix PR Checks safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fix PR Checks use?

Fix PR Checks is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fix PR Checks use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fix PR Checks?

Skills that share tags, products or a category with Fix PR Checks: Akb Ingest (dnotitia/akb, 162 stars), Load PR Comments (NeoLabHQ/context-engineering-kit, 1.8k stars), Vibe Kanban (aiskillstore/marketplace, 433 stars) and Skill Seekers Builder (yusufkaraaslan/Skill_Seekers, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix PR Checks?

adamayoung (a GitHub user) maintains it in adamayoung/TMDb, which has 178 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 3, 2026.

Source: adamayoung/TMDb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.