Skip to main content
hc
Submit
statuslinesSource-backed
GitHub logo

GitHub Check Runs Statusline

Claude Code statusline that reads GitHub REST check runs for the active pull request head commit and summarizes failed, pending, and passing checks.

by MkDev11·added 2026-06-04·
Claude Code
HarnessClaude Code
Language:bash
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/statuslines/github-check-runs-statusline
Source URLs
https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json, https://github.com/github/rest-api-description
Brand
GitHub
Brand domain
github.com
Brand asset source
brandfetch
Safety notes
Check-run counts are a review prompt, not proof that every required branch protection rule is satisfied., Repositories with more than 100 check runs may need pagination or a slower dedicated dashboard., Keep the refresh interval moderate so the statusline does not repeatedly query GitHub APIs.
Privacy notes
The script prints aggregate check-run counts and the pull request number., Private repository metadata follows the local GitHub CLI account and may appear in terminal recordings., The statusline does not print check names, workflow names, branch names, or commit messages.
Author
MkDev11
Submitted by
MkDev11
Claim status
unclaimed
Last verified
2026-06-04

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Config edit

Copy-ready — paste the snippet to get started.

Install command

Not provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

3 to clear

Platforms

1 listed

Install type

Config edit

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup. Have accounts and credentials ready first.

0/3 ready
Account & credentials1Install & runtime1General1

Safety & privacy surface

Safety & privacy surface

3 safety and 3 privacy notes across 3 risk areas. Review closely: network access.

3 areas
  • SafetyExecution & processesCheck-run counts are a review prompt, not proof that every required branch protection rule is satisfied.
  • SafetyExecution & processesRepositories with more than 100 check runs may need pagination or a slower dedicated dashboard.
  • SafetyGeneralKeep the refresh interval moderate so the statusline does not repeatedly query GitHub APIs.
  • PrivacyNetwork accessThe script prints aggregate check-run counts and the pull request number.
  • PrivacyGeneralPrivate repository metadata follows the local GitHub CLI account and may appear in terminal recordings.
  • PrivacyGeneralThe statusline does not print check names, workflow names, branch names, or commit messages.

Safety notes

  • Check-run counts are a review prompt, not proof that every required branch protection rule is satisfied.
  • Repositories with more than 100 check runs may need pagination or a slower dedicated dashboard.
  • Keep the refresh interval moderate so the statusline does not repeatedly query GitHub APIs.

Privacy notes

  • The script prints aggregate check-run counts and the pull request number.
  • Private repository metadata follows the local GitHub CLI account and may appear in terminal recordings.
  • The statusline does not print check names, workflow names, branch names, or commit messages.

Prerequisites

  • GitHub CLI installed and logged in for the repository.
  • jq available for counting GitHub REST check-run states.
  • The current branch has an associated pull request and the account can read check runs for its head commit.

Schema details

Install type
config
Troubleshooting
No
Source repository stats
Scope
Source repo
Runtime and command metadata
Script language
bash
Script body
#!/usr/bin/env bash
set -u

main() {
if ! command -v gh >/dev/null 2>&1; then
  echo "checks: gh missing"
  exit 0
fi
if ! command -v jq >/dev/null 2>&1; then
  echo "checks: jq missing"
  exit 0
fi

pr_json=$(gh pr view --json number,headRefOid 2>/dev/null || true)
if [ -z "$pr_json" ]; then
  echo "checks: no active PR"
  exit 0
fi

pr_number=$(printf '%s' "$pr_json" | jq -r '.number // empty')
head_sha=$(printf '%s' "$pr_json" | jq -r '.headRefOid // empty')
repo=$(gh repo view --json nameWithOwner --jq '.nameWithOwner' 2>/dev/null || true)
if [ -z "$pr_number" ] || [ -z "$head_sha" ] || [ -z "$repo" ]; then
  echo "checks: unavailable"
  exit 0
fi

runs=$(gh api "repos/$repo/commits/$head_sha/check-runs?per_page=100" 2>/dev/null || true)
if [ -z "$runs" ]; then
  printf 'checks: PR #%s | unavailable\n' "$pr_number"
  exit 0
fi

fail=$(printf '%s' "$runs" | jq '[.check_runs[]? | select((.conclusion // "") | test("failure|cancelled|timed_out|action_required"; "i"))] | length')
pending=$(printf '%s' "$runs" | jq '[.check_runs[]? | select((.status // "") != "completed")] | length')
pass=$(printf '%s' "$runs" | jq '[.check_runs[]? | select((.conclusion // "") == "success")] | length')

printf 'checks: PR #%s | fail %s | pending %s | pass %s\n' "$pr_number" "$fail" "$pending" "$pass"
}

case $- in
  *n*) ;;
  *) main "$@" ;;
esac
Full copyable content
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/github-check-runs-statusline.sh"
  }
}

About this resource

Source notes

  • GitHub's REST API description includes the check-runs endpoint for listing check runs on a Git reference.
  • This entry uses check-run state from the REST API rather than the GitHub CLI gh pr checks manual page that overlaps the existing repository-health statusline source domain.

Duplicate check

Checked existing statuslines, live HeyClaude statuslines, open pull requests, and repository content for github-check-runs-statusline, check runs, GitHub checks, and gh-pr-checks-statusline. The earlier CLI-docs submission was closed for overlapping cli.github.com; this replacement uses a different canonical source, title, slug, and REST check-run scope.

Disclosure

Editorial statusline recipe. No paid placement or affiliate link is used.

#github#ci#checks#claude-code

Source citations

Add this badge to your README

Show that GitHub Check Runs Statusline is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/statuslines/github-check-runs-statusline.svg)](https://heyclau.de/entry/statuslines/github-check-runs-statusline)

How it compares

GitHub Check Runs Statusline side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field
GitHub logoGitHub Check Runs Statusline

Claude Code statusline that reads GitHub REST check runs for the active pull request head commit and summarizes failed, pending, and passing checks.

Open dossier
GitHub logoPR Closing Keywords Statusline

Claude Code statusline that checks the active pull request body for GitHub closing keywords and shows whether issue auto-closure linkage is present.

Open dossier
GitHub logoGitHub Repository Health Statusline

Claude Code statusline that uses GitHub CLI to show repository health basics: archive state, open PR count, open issue count, and default branch.

Open dossier
GitHub logoGitHub Search Review Queue Statusline

Claude Code statusline that uses GitHub pull request search qualifiers to show review-requested queue counts for maintainers.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterMkDev11MkDev11MkDev11MkDev11
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandGitHub logoGitHubGitHub logoGitHubGitHub logoGitHubGitHub logoGitHub
Categorystatuslinesstatuslinesstatuslinesstatuslines
SourceSource-backedSource-backedSource-backedSource-backed
AuthorMkDev11MkDev11MkDev11MkDev11
Added2026-06-042026-06-042026-06-042026-06-04
Platforms
Claude Code
Claude Code
Claude Code
Claude Code
Harness
Claude Code
Claude Code
Claude Code
Claude Code
Source repo————
Safety notes✓Check-run counts are a review prompt, not proof that every required branch protection rule is satisfied. Repositories with more than 100 check runs may need pagination or a slower dedicated dashboard. Keep the refresh interval moderate so the statusline does not repeatedly query GitHub APIs.✓Closing keywords are workflow signals, not proof that the PR actually satisfies the linked issue. Some repositories use manual issue closure or external trackers, so missing keywords should be interpreted with project policy. Keep automated PR body edits separate from this read-only statusline.✓Repository counts are orientation signals and should not replace issue triage, release gates, or maintainer review. The `--limit 100` query cap keeps the statusline fast; very large queues may need a dedicated dashboard. The script does not modify repository settings, issues, or pull requests.✓Queue counts help with triage but do not rank urgency, security impact, or release blockers. Draft PRs are excluded from the ready count, but repositories may use labels or checks for additional readiness rules. Keep the refresh interval moderate to avoid repeated GitHub search calls.
Privacy notes✓The script prints aggregate check-run counts and the pull request number. Private repository metadata follows the local GitHub CLI account and may appear in terminal recordings. The statusline does not print check names, workflow names, branch names, or commit messages.✓The script prints only aggregate closing-reference counts and the pull request number. It reads the pull request body, which can contain private planning details in private repositories. Private repository access follows the local GitHub CLI account and organization policy.✓The statusline prints repository owner/name, counts, default branch, and state. Private repository metadata follows the local GitHub CLI login and may appear in terminal screenshots. Organization policies can restrict which counts are visible to the local account.✓The script prints aggregate counts only, not PR titles, authors, or branch names. Private review requests follow the local GitHub account and may reveal workload size in screenshots. Organization review-team rules may cause counts to differ from the GitHub web UI.
Prerequisites
  • GitHub CLI installed and logged in for the repository.
  • jq available for counting GitHub REST check-run states.
  • The current branch has an associated pull request and the account can read check runs for its head commit.
  • GitHub CLI installed and logged in for the current repository.
  • jq available for reading pull request JSON.
  • The current branch has an associated pull request with a body that can be read by the local account.
  • GitHub CLI installed and logged in with access to the current repository.
  • jq available for reading GitHub CLI JSON output.
  • A refresh interval that respects repository size and GitHub API rate limits.
  • GitHub CLI installed and logged in as the maintainer account whose review queue should be shown.
  • jq available for counting pull request fields.
  • Repository access that lets GitHub search return pull requests requesting the current account's review.
Install————
Config
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/github-check-runs-statusline.sh"
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/pr-closing-keywords-statusline.sh"
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/gh-repo-health-statusline.sh"
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/github-search-review-queue-statusline.sh"
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

GitHub logo

Claude Code GitHub Actions Review Workflow

Automate PR review with Claude Code GitHub Actions using official setup steps.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev
GitLab logo

Claude Code GitLab CI/CD Workflow

Run Claude Code in GitLab CI with least-privilege tools, review gates, and provider options.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Adding Plugin Install Hints to Developer CLIs

Write a claude-code-hint tag to stderr under CLAUDECODE, and Claude Code prompts users once to install your official-marketplace plugin.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JPette1783

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.