gh

Investigate GitHub commits and create pull requests via GitHub CLI.

12|2|Updated May 19, 2026
One-click install
npx skills add https://github.com/har-ki/claude-code-sre-handbook --skill gh-har-ki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh
Source: https://github.com/har-ki/claude-code-sre-handbook/tree/main/skills/gh
Command: npx skills add https://github.com/har-ki/claude-code-sre-handbook --skill gh-har-ki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you investigate GitHub activity and create pull requests to fix code by using the GitHub CLI instead of manually browsing commits, diffs, and issues.

Core Features & Use Cases

  • Commit & PR investigation: Lists recent commits and open PRs, so you can quickly understand what changed and what’s currently in progress.
  • Safe, guided PR creation: Uses confirmation gates for edits and PR creation, then opens the PR for the user to review.
  • Deterministic repo fix workflow: Clones into a unique temporary working directory, edits via absolute paths, verifies diffs, pushes the branch, and cleans up automatically.

Quick Start

Provide the repository and branch, then ask me to investigate recent commits and prepare a PR that fixes the bug you described.

Frequently Asked Questions about gh

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate recent commits in a GitHub repository using the CLI?

The workflow uses a deterministic repository fix process that clones into a unique temporary working directory, edits files via absolute paths, verifies diffs, pushes the branch, and cleans up automatically after creating the pull request.

Do I need to manually confirm CLI commands when investigating GitHub issues?

No, investigating GitHub issues uses read-only API commands without confirmation. Confirmation gates are only applied to guarded write operations like code edits and pull request creation to ensure safe execution.

Can I use the GitHub CLI to fix code and open a pull request from a temporary workdir?

Yes, the workflow clones into a unique temporary working directory, edits files via absolute paths, verifies diffs, pushes the branch, and cleans up automatically after opening the pull request for you to review.

What is the best way to automate creating pull requests for identified code fixes?

Using GitHub CLI workflows to create pull requests for code fixes provides a safe, guided process. It applies confirmation gates for edits and PR creation, then opens the PR for review rather than blindly committing.

Are there limitations when using temporary workdirs for GitHub CLI repository fixes?

The temporary workdir approach requires explicit user confirmation for write operations and safe git operations. It is limited to tasks referencing GitHub repos, recent changes, issues, or PRs, and does not perform unguarded automated commits.