gh-claude
A modern, keyboard-first TUI for managing GitHub issues and pull requests across multiple repositories. It uses Textual for the interface, GitHub CLI for data, and Claude Code for issue drafting and analysis.
License: MIT
PyPI: gh-claude
Repository: masaaaaa725/ghc
Requirements
- Python 3.13+
- uv or pip
- GitHub CLI (
gh auth login) - Claude Code (
claude) - Git
Install
pip install gh-claude
# or
uv tool install gh-claude
Update an existing uv tool install:
uv tool upgrade gh-claude
Publishing
Every push to main runs .github/workflows/publish.yml,
which bumps the patch version in pyproject.toml, publishes that version to PyPI,
and commits the bump back to main (with [skip ci] to avoid a loop).
One-time setup on PyPI (Trusted Publishing):
- Open PyPI publishing settings for gh-claude
- Add a GitHub publisher:
- Owner:
masaaaaa725 - Repository:
ghc - Workflow:
publish.yml - Environment:
pypi
- Owner:
- In GitHub, create an Environment named
pypi(Settings → Environments)
After that, merges to main publish automatically. Users can then run
uv tool upgrade gh-claude.
Run
gh-claude
# alias
ghc
From a local checkout:
uv sync
uv run gh-claude
The app detects the GitHub repository in the current directory. Press r or
Ctrl+P to switch to any repository returned by gh repo list.
Choosing a Claude model
By default, ghc uses whatever model the claude CLI defaults to. Set a
starting model with the --model flag:
ghc --model claude-opus-4-6
To avoid passing the flag every time, set the GHC_MODEL environment variable,
or persist a default in ~/.config/ghc/config.toml:
model = "claude-sonnet-4-6"
Precedence: --model flag > GHC_MODEL environment variable > config file >
the claude CLI's own default.
Press m at any time inside ghc to switch models without restarting — pick
a preset or type any model ID. The active model is shown in the footer.
Keyboard shortcuts
↑/↓: move the selection in the Issues or Pull Requests list←/→: switch between the Issues and Pull Requests tabsf: cycle the status filter (OPEN→CLOSED→ALLfor Issues; includesMERGED/DRAFTfor PRs)r/Ctrl+P: searchable repository picker (↑/↓to move,Enterto select,Escto cancel)c: turn rough notes into a reviewed GitHub issue with Claudes: summarize the selected issue or pull request with Claudeo: check out the selected pull request as a local branchv: review the selected pull request diff with Claudea: draft, preview, and post an AI-polished commentCtrl+E: create an Issue branch and let Claude implement the selected Issuei/p: switch to Issues / Pull RequestsCtrl+R/F5: refresh Issues and Pull Requests for the current repositoryCtrl+C: quit
Project layout
.
├── pyproject.toml
├── uv.lock
├── src/ # Import package `ghc` (PyPI name: `gh-claude`)
│ ├── __init__.py
│ ├── __main__.py
│ ├── app.py # Main Textual app and interactions
│ ├── app.tcss # Dark UI theme
│ ├── clients.py # Async gh / claude / git wrappers
│ ├── models.py # Domain models
│ └── screens.py # Repository and issue workflow modals
└── tests/
├── test_app.py
├── test_clients.py
├── test_models.py
└── test_screens.py
All external commands are executed without a shell via
asyncio.create_subprocess_exec. GitHub read operations request JSON explicitly;
commands such as gh pr diff, gh pr checkout, gh issue create, and
gh issue comment are exceptions because those GitHub CLI commands do not
support --json.
Ctrl+E is intentionally limited to the repository currently checked out on
disk. After confirmation, it creates issue-<number>-<slug> with
git checkout -b, then runs Claude Code in print mode. Claude is instructed not
to commit, push, or modify unrelated files; always review the working tree after
it finishes.
Test
uv run pytest
Metadata
Release files for gh-claude 0.5.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gh_claude-0.5.2.tar.gz | 27.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gh_claude-0.5.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.2 kB
Release files / gh_claude-0.5.2.tar.gz
| Download URL | gh_claude-0.5.2.tar.gz |
|---|---|
| Size | 27.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4ab68b8887620391b68b2bb42f041382a9c4f19b77758e97100d5c75dcdff9b
|
|
BLAKE2b-256 checksum How to use checksums |
edfc3dd60fcc6d037a69a0c24cc400306df937e5017572ec9cb161cbae2294c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.10 {"installer":{"name":"uv","version":"0.12.10","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / gh_claude-0.5.2-py3-none-any.whl
| Download URL | gh_claude-0.5.2-py3-none-any.whl |
|---|---|
| Size | 23.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
20459037b0985e63cf72ada288c36d64bf19b5b40505d31e43623dbac5ba4483
|
|
BLAKE2b-256 checksum How to use checksums |
c5583de2684baa3ca9d10e3a7124f73aad995578e227cbbcd98b2f8475ddf864
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.10 {"installer":{"name":"uv","version":"0.12.10","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for gh-claude 0.5.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.