gh-dash: GitHub PR Dashboard

VerifiedCaution

Provides a GitHub pull request dashboard directly in the terminal. Use to view PR status, CI/CD progress, and merge without leaving Claude Code.

Sby Skills Guide Bot
DevOpsBeginner
7/23/2026
Claude Code
#github#pull-request#ci-cd#merge#code-review

Recommended for

Automated summary

Renders a GitHub pull request dashboard in the terminal through the gh CLI, with CI/CD tracking and one-command merging.

Strengths

  • Consolidates PR metadata, CI results, and changed files into a single view without leaving Claude Code
  • Separates and summarizes automated reviewer comments (CodeRabbit, Cursor Bugbot, coverage bots) from human reviews
  • Checks branch protection rules, required reviews, and status checks before attempting a squash, merge, or rebase merge
  • Shows a CI progress bar with elapsed times and links to full logs for failing checks

Limitations

  • Relies entirely on the gh CLI being installed and authenticated with sufficient repository permissions
  • GitHub only: no support for GitLab, Bitbucket, or other forges
  • Cannot bypass branch protection; it only surfaces blockers before a merge attempt
When to use it

Use it when you need to check a PR's status, watch CI progress, or merge a branch from the terminal.

When not to use it

Skip it if the repository is not hosted on GitHub or the gh CLI is unavailable or unauthenticated.

Security analysis

Caution
Quality score85/100

The skill is a straightforward wrapper around the GitHub CLI for viewing PR status, CI checks, bot comments, and performing merges. Nothing is obfuscated or exfiltrating, and commands map to well-known `gh` subcommands. The rating is caution rather than safe because it relies on an authenticated Bash tool with write permissions and can execute irreversible merges and remote branch deletions without an explicit confirmation gate, plus it declares write tools it doesn't need.

Findings
  • •Skill drives authenticated `gh` CLI via Bash to mutate remote state: example workflow runs `gh pr merge --squash --delete-branch`, which merges code and deletes the remote branch; the instructions do not require an explicit user confirmation step before executing the merge, so an ambiguous prompt could trigger an irreversible remote action.
  • •Uses an already-authenticated `gh` session with the user's full repo permissions (write access for merging); the trust boundary is the user's GitHub token, and the skill has no scoping or read-only guardrails.
  • •Declares write-capable tools (Write, Edit) and Glob/Grep that the described read-only dashboard and `gh` commands do not require — a least-privilege concern, not an active risk.
  • •No obfuscated payloads, no curl|sh, no secret/token exfiltration, no safety-disabling instructions; all commands are conventional, documented `gh` subcommands.
How this analysis is made

Examples

Check PR status
Show me the PR dashboard for my current branch and tell me if anything is blocking the merge.
Monitor CI
How are the CI checks doing on this PR? Show me any failing jobs and their logs.
Merge PR
Squash merge this PR once the required checks pass, then delete the remote branch and check out main.

name: gh-dash description: | Provides a GitHub pull request dashboard directly in the terminal. Use when the user wants to view PR status, check CI/CD progress, review bot comments, or merge pull requests without leaving Claude Code. Trigger with phrases like "show PR dashboard", "PR status", "check CI progress", "merge this PR", or "review pull request". allowed-tools: Read, Write, Edit, Bash, Glob, Grep version: 1.0.0 author: Jake Kozloski jakozloski@gmail.com license: MIT compatible-with: claude-code tags: [github, pull-request, ci-cd, dashboard, devops, merge, code-review]

gh-dash

GitHub pull request dashboard for Claude Code with CI/CD monitoring and merge capabilities.

Overview

This skill brings a complete GitHub pull request dashboard into your terminal workflow. Instead of switching to a browser to check PR status, review CI results, or merge branches, gh-dash consolidates all PR information into a single view. It displays real-time CI/CD progress with a visual progress bar, detects and summarizes bot comments (CodeRabbit, Cursor Bugbot, Coverage reporters), shows files changed with line-level statistics, and provides one-command merge operations with support for squash, merge commit, and rebase strategies.

The skill relies on the GitHub CLI (gh) for all API interactions, so it works with any GitHub repository where you have appropriate permissions. It respects branch protection rules, required reviews, and status checks, surfacing any blockers clearly before allowing merge operations.

Instructions

  1. View PR status for the current branch:

    • Navigate to the repository directory
    • Ask: "Show me the PR dashboard" or "What's the status of my PR?"
    • The skill runs gh pr view and gh pr checks to gather PR metadata, review status, and CI results
  2. Check CI/CD progress:

    • Ask: "How are the CI checks doing?" or "Is CI passing?"
    • The skill displays each check with its status (pass, fail, pending), elapsed time, and a visual progress indicator
    • Failed checks include the failure reason and a link to the full log
  3. Review bot comments:

    • Ask: "What did the bots say?" or "Show code review comments"
    • The skill filters PR comments to identify automated reviewers (CodeRabbit, Dependabot, coverage bots) and summarizes their findings separately from human reviews
  4. Merge the PR:

    • Ask: "Merge this PR" or "Squash merge"
    • Supported strategies: squash (default), merge, rebase
    • The skill checks for required reviews, passing CI, and branch protection before attempting the merge
    • After merging, it optionally deletes the remote branch and checks out the default branch
  5. View file changes:

    • Ask: "What files changed in this PR?"
    • Displays a summary of files added, modified, and deleted with line counts

Output

The skill produces formatted terminal output covering:

  • PR Summary: Title, description, author, branch, labels, reviewers, and age of the PR.
  • CI/CD Status Table: Each workflow check listed with status icon, check name, elapsed time, and conclusion. A progress bar shows overall completion percentage.
  • Bot Comment Summary: Grouped by bot type, showing the number of comments, key findings (e.g., "CodeRabbit found 3 suggestions"), and links to individual comments.
  • Files Changed: Table of modified files with insertions/deletions counts and file type indicators.
  • Merge Result: Confirmation of merge strategy used, resulting commit SHA, and branch cleanup status.

Examples

Example 1: Quick PR Status Check

User: "What's the status of my PR?"

The skill will:

  1. Run gh pr view --json title,state,reviews,statusCheckRollup,additions,deletions,changedFiles to gather data.
  2. Display a formatted summary showing the PR title, review approvals, and CI status.
  3. Highlight any blockers: failing checks, requested changes, or missing required reviews.

Example 2: Merge After CI Passes

User: "Merge this PR with squash."

The skill will:

  1. Verify all required status checks are passing with gh pr checks.
  2. Confirm the PR has sufficient approvals.
  3. Execute gh pr merge --squash --delete-branch to squash-merge and clean up the branch.
  4. Report the merge commit SHA and confirm the remote branch was deleted.

Example 3: Review Bot Feedback

User: "Summarize the bot comments on this PR."

The skill will:

  1. Fetch all PR comments with gh api repos/{owner}/{repo}/pulls/{number}/comments.
  2. Identify automated comments by known bot usernames and patterns.
  3. Group findings by bot: CodeRabbit suggestions, coverage report deltas, security scan results.
  4. Present a concise summary with links to the full comments for follow-up.

Prerequisites

  • GitHub CLI (gh) must be installed and authenticated (gh auth status to verify).
  • The current directory must be inside a git repository with a GitHub remote.
  • Appropriate permissions for the operations requested (write access for merging).

Error Handling

  • No PR found for current branch: Suggests creating a PR with gh pr create or checking out the correct branch.
  • CI checks still running: Reports which checks are pending and offers to wait or proceed.
  • Merge blocked: Clearly states the blocking reason (failed checks, missing reviews, branch protection) and suggests remediation steps.
  • GitHub CLI not installed: Detects missing gh command and provides installation instructions for the current platform.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/gh-dash-github-pr-dashboard-mrx3xy8x/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/gh-dash-github-pr-dashboard-mrx3xy8x' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/gh-dash-github-pr-dashboard-mrx3xy8x/download' --output '.skill-downloads/gh-dash-github-pr-dashboard-mrx3xy8x/SKILL.md.part' && mv '.skill-downloads/gh-dash-github-pr-dashboard-mrx3xy8x/SKILL.md.part' '.skill-downloads/gh-dash-github-pr-dashboard-mrx3xy8x/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Edit, Bash, Glob, Grep

Original excerpt: Prerequisites
  • GitHub CLI (gh) must be installed and authenticated (gh auth status to verify).
  • The current directory must be inside a git repository with a GitHub remote.
  • Appropriate permissions for the operations requested (write access for merging).

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/gh-dash-github-pr-dashboard-mrx3xy8x/SKILL.md' && test -s '.skill-downloads/gh-dash-github-pr-dashboard-mrx3xy8x/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/gh-dash' && cp -R '.skill-downloads/gh-dash-github-pr-dashboard-mrx3xy8x' '.claude/skills/gh-dash'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/gh-dash-github-pr-dashboard-mrx3xy8x'

openskills read 'gh-dash-github-pr-dashboard-mrx3xy8x'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/gh-dash-github-pr-dashboard-mrx3xy8x/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills