Skip to content
Menu
WorkflowSkills, tmux and the daily loopToolsai-usagebarQuota and reset times for 24 AI providersghpendingEvery open PR and issue in one listtclockA terminal clock with command widgetsai-memoryLong-term memory for coding agentsai-jailAn OS sandbox for AI coding agentsWritingThe blog and the LLM benchmarkNewsletterThe M.Akita Chronicles, every MondayPodcastsLong conversations about AI, on videoGamesMy game collection as code, on OmarchySetupOmarchy, tmux, and what I set asideFollow
ghpending

Every open pull request and issue, in one list

ghpending fetches every repository you track at once and prints what is waiting, with the work that needs you first. It is the first widget on my second monitor and the reason I know which projects need a morning.

ghpending output in a terminal. Under akitaonrails/FrankMD: five Dependabot pull requests and three issues. Under akitaonrails/FrankMega: six Dependabot pull requests. FrankClaw and FrankSherlock show nothing pending.

Forty repositories, one glance

GitHub's notifications mix everything with everything. ghpending asks one question per repository, what is open right now, and answers it for all of them in a few seconds.

Twelve repository folders, five glowing. Amber lines from the glowing ones converge into one digest list with red SEC alerts at the top, violet pull requests and amber issues. In the corner, a Fork arrow points to Upstream.

Details that save the morning

Forks follow upstream

When a tracked repo is a fork, you see your pull requests on the original project instead of the fork's own empty queue. Detected automatically and cached.

Security alerts first

For repos you own: Dependabot, secret scanning and code scanning alerts, tagged SEC or QUA and sorted by severity ahead of everything else.

Your items step back

Pull requests you opened are dimmed and listed last, marked "by you", because they are waiting on other people.

Feedback stands out

Comment counts and review decisions show wherever the API has them, highlighted when there is something to read.

Sort by what matters today

Most recent activity, name, most open items, or the most neglected repository first. --limit caps the list fairly across repos.

Fast with a token

With GITHUB_TOKEN, all repos come in one batched GraphQL request, private ones included. Without it, public repos still work.

Use it

Pick the repositories once. After that it is one word.

ghpending
ghpending add                 # pick repos to trackghpending                     # print the digestghpending --sort stale        # most neglected repo firstghpending --subscribed        # only what you followGITHUB_TOKEN=$(gh auth token) ghpending

Install

terminal
brew tap akitaonrails/tap && brew install ghpending
Configuration, proxy and all flags in the README

Everything here is open source

The tools, the skills and the benchmark are public repositories. Fork them and build the version that fits the way you work.