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 pr        # current branch's PR: status, checks, and review comment
                # threads (unresolved by default; --all also shows resolved)
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)
wazup repos     # local checkouts wazup has seen, most-recently-seen first
                # (optionally filtered: wazup repos <name-or-path substring>)
wazup install-skills  # install wazup's Claude Code skill to ~/.claude/skills/

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).

Running wazup, wazup ci, wazup pr, wazup my, wazup review, wazup issues, or wazup release inside a repo also registers that checkout (path, repo, branch) in a local registry at ~/.local/share/wazup/repos.jsonl — no opt-in needed. wazup repos lists what's been seen so far, letting an AI agent find a local checkout of a repo by name instead of guessing paths or re-cloning it.

Run wazup install-skills to install a Claude Code skill documenting all of this (~/.claude/skills/wazup/SKILL.md), so an agent picks up when and how to reach for wazup on its own. Every command but install-skills itself prints a one-line nudge to stderr, once a day at most, when the installed copy has fallen behind the version bundled with your installed wazup.

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