1. Habit
  2. Skills
  3. GitHub CLI skill
paulrberg · 3K installs

GitHub CLI skill
Runs by itself, a CI run fails.

Failing CI gets triaged fast.

Install the GitHub CLI skill and make it a habit: follow https://gethabit.dev/skills/paulrberg/cli-gh.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

3K installs101 starsMIT licenceSource on GitHub ↗

GitHub CLI

by paulrberg · 3K installs

The skill

The github cli skill (cli-gh) helps agents use gh for repository reads, workflow runs, search, releases and configuration, with a bounded CI failure triage workflow.

Only when you ask.

The habit

Failing CI gets triaged fast.

↻ Runs by itselfa CI run fails

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

a CI run fails. Runs in GitHub Actions or Claude Code routine.

  • ↻ a CI run fails
  • workflow_run.conclusion == failure

02

It checks its work

new run passes. If a check fails, it tells you.

  • ✓gh run watch --exit-status exits zero on the new run
  • ✓the run URL comes back from gh run view --json url
  • ✓local tool versions match the pins in .github/workflows/*.yml

03

It remembers

CI failure log. The next run reads it first: past failures with their causes and fixes.

loops/ci-triage-loop/runs.md

One run, step by step.
Then it stops.

Stop ruleStops after five failing runs and one fix attempt per run.

  1. 01

    Find failing runs

    gh run list with --status failure and --limit 5 lists failures for the branch or commit.

  2. 02

    Extract failed lines

    gh run view --log-failed, filtered with rg and head, keeps only error lines.

  3. 03

    Check toolchain drift

    Compare versions pinned in .github/workflows/*.yml with the local --version output.

  4. 04

    Fix the cause

    Only when you asked for fixes, the agent fixes the cause and pushes the commit.

  5. 05

    Watch the new run

    gh run watch with --exit-status follows the new run to the end.

  6. 06

    Report the result

    The run URL and final status go into the run log.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the GitHub CLI skill helps.

Use it when

  • ✓ A CI run fails
  • ✓ You need gh command syntax
  • ✓ You read repo data from the shell

Skip it when

  • – You write PRs or issues
  • – You need to delete repositories

Questions

GitHub CLI skill, answered.

Can it delete runs or caches?

No. The skill never deletes workflow runs, caches, releases, secrets or repositories.

Does it comment on the pull request?

No. Pull request and issue writes belong to the yeet skill, which this loop does not call.

How do I install the GitHub CLI skill?

Copy the prompt at the top into your agent. It installs the skill from paulrberg/agent-skills and sets up the habit. Or run npx skills add paulrberg/agent-skills --skill cli-gh.

Is the GitHub CLI skill free?

Yes. It is published under MIT. Habit is free too.

GitHub CLI. Now as a habit.

Install the GitHub CLI skill and make it a habit: follow https://gethabit.dev/skills/paulrberg/cli-gh.md

  • Free
  • No account
  • Undo in one line

All paulrberg skills →More ops skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by paulrberg, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.