pitboss
Sweep a project’s pull requests, merge queue, local checkouts and worker slots, and say what each calls for.
pitboss reads the project’s state from GitHub (through gh api, with the session’s own authentication) and from the checkouts on the machine, and prints one line per thing that needs a look. Every line that calls for an action starts with a marker in capitals and says the action. Everything about one project (its repositories, review format, models, labels, paths) lives in that project’s configuration file; pitboss itself names no project.
Commands
pitboss sweep CONFIG |
PRs, runner pressure, queue runs, stragglers, worktrees, reminders, slots. Exits 1 on a red or conflicted PR. |
pitboss pressure CONFIG |
One line; exits 1 under runner pressure. |
pitboss cancel-stale-runs CONFIG |
Cancel superseded merge-queue runs (--no-dry-run). |
pitboss clean-worktrees CONFIG |
Remove finished worktrees (--no-dry-run). |
pitboss review-form CONFIG REPOSITORY |
The form a review comment there must take. |
pitboss slots ACTION CONFIG ... |
The worker-slot ledger, and what to start next. |
CONFIG is a path, or a name looked up as .claude/pitboss/<name>.toml in the current directory or a parent. doc/example.toml lists every key.
The sweep skill
The repository is also a Claude Code plugin marketplace with one plugin, pitboss, whose sweep skill says when to run pitboss and what to do about every line. A project enables it in its .claude/settings.json:
{
"extraKnownMarketplaces": {
"pitboss": {"source": {"source": "github", "repo": "dev-skill-up/pitboss"}}
},
"enabledPlugins": {"pitboss@pitboss": true}
}skill-zips/sweep.zip is the same skill for upload to claude.ai.
Development
nox runs every check: tests (100% branch coverage), lint (black and stolid), mypy, docs, skills (the skill’s files, the markers against the references, and skill-zips/), dry_release. The design, and how each value specific to one project became configuration, is in doc/design.rst.
1 maintainer
Metadata
1 maintainer
Release files for pitboss 2026.10.21.9634
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 | |
|---|---|---|---|---|
| pitboss-2026.10.21.9634.tar.gz | 50.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pitboss-2026.10.21.9634-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 112.1 kB
Release files / pitboss-2026.10.21.9634.tar.gz
| Download URL | pitboss-2026.10.21.9634.tar.gz |
|---|---|
| Size | 50.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
01d538782aef89785842e8389b43b76b3459825a44021f94e651a8d69ea93b63
|
|
BLAKE2b-256 checksum How to use checksums |
f805f521bb4b621429d071c31141e82ad77ba2855a5163022b816ff889efe70a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / pitboss-2026.10.21.9634-py3-none-any.whl
| Download URL | pitboss-2026.10.21.9634-py3-none-any.whl |
|---|---|
| Size | 61.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63835e9e682f45790ef89b72c78cb3929ddee44fe33244a756d8c46061cd4c77
|
|
BLAKE2b-256 checksum How to use checksums |
ba7fd5bc8390977580f4216397af2f7f91111fde2b39815779fd9ec2a03244fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for pitboss 2026.10.21.9634
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.
