Skip to main content

wazup

What's up with this repo, right now. A thin CLI over gh and git that shows your current branch's PR and CI status without you having to open a browser.

Requires the GitHub CLI (gh) to be installed and authenticated (gh auth login).

Commands

wazup           # repo, branch, PR, and CI status for the current directory
                # (recent local branches, with their PR if any, when on the
                # default branch with no PR of its own)
wazup ci        # just the CI status for the current branch/PR
wazup my        # your open PRs in this repo, or (outside a repo) your PRs
                # with activity in the last 7 days, across all repos
wazup review    # PRs awaiting your review, updated in the last 7 days
wazup issues    # your open issues in this repo, or (outside a repo) your
                # open issues with activity in the last 7 days, across all repos
wazup slop      # flag AI-slop phrasing (stock phrases, "not just X but Y"
                # sentence shapes) in your uncommitted diff (or, with
                # --all, every file in the directory)

Add -w/--why to wazup or wazup ci to drill into a failing check — prints the tail of the failing job's log, right up to the error.

wazup also keeps the active gh account in sync with whichever repo you're in, switching it (permanently, like running gh auth switch by hand) when the repo's owner doesn't match.

If wazup flags uv.lock as pointing at a private index/mirror (e.g. a corporate PyPI proxy baked in via ~/.config/uv/uv.toml) instead of public PyPI, run wazup fixup uv-lock to rewrite it back to pypi.org / files.pythonhosted.org — a plain uv lock re-resolves against the same mirror and just reintroduces the leak, so rerun the fixup after that if needed.

Run wazup slop before committing to catch stock AI phrasing (delve into, it's important to note that, not just X but Y, ...) in the added lines of your uncommitted diff (git diff HEAD). Outside a git repo it scans every file in the directory instead; pass --all to do that even inside one, or pipe text in with --stdin (e.g. a draft commit message or PR description: git log -1 --format=%B | wazup slop --stdin).

Usage in an AI coding client

wazup is built to be run straight from an AI coding assistant (e.g. Claude Code) via its shell-passthrough, like !wazup. Running the single command gets the assistant repo/branch/PR/CI status in one shot, instead of it making several separate gh/git calls and spending tokens piecing the results together itself.

Install

uv tool install wazup

License

MIT

Release files for wazup 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for wazup 0.4.0
File Size Uploaded
wazup-0.4.0.tar.gz 21.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for wazup 0.4.0
File Interpreter ABI Platform
wazup-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 43.8 kB

Release files / wazup-0.4.0.tar.gz

Download URL wazup-0.4.0.tar.gz
Size 21.0 kB
Tags Source
SHA-256 checksum
How to use checksums
b3a68f41f5cb85c63f8c10a1f39c8e22eea4abb162389c0aaeeb260f60f149b4
BLAKE2b-256 checksum
How to use checksums
d4db3734f74b1c36139b45f1ed00a9f6d231649153eaa5af95bdc6bdcb237fc9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 25, 2026.

Transparency log

Release files / wazup-0.4.0-py3-none-any.whl

Download URL wazup-0.4.0-py3-none-any.whl
Size 22.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c20f9d85c8d6da8876f775f16b7d60f9628966caec58d12a03664569a03ab6e5
BLAKE2b-256 checksum
How to use checksums
dd03fcd51d2663db7e4135231825b7175602ebe9bc2e7d9449fb9305e6a1a805
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 25, 2026.

Transparency log

Release history Release notifications | RSS feed

0.5.0

2 release files

This release

0.4.0 This release

2 release files

0.3.0

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.0

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page