Use this agent when git operations are needed, such as staging changes, creating commits, managing branches, or organizing work into logical commits. This includes after completing a feature, fixing a bug, or any time code changes need to be committed.\n\nExamples:\n\n- User: "I just finished implementing the login…
Use this agent when code needs to be refactored for simplicity, elegance, and clarity. This includes when code has accumulated technical debt, contains duplication, feels bloated, or could benefit from architectural simplification. Also use it after implementing a feature to review whether the implementation is as…
Cut a Bartleby release the way this repo expects: enforce the on-main / clean / synced preconditions, dry-run scripts/release.py, PAUSE for explicit confirmation, then publish the tag + GitHub Release. Use whenever asked to cut, publish, or tag a release.
Land one or more issue-branches onto a target branch, tested and reviewed, and open the PRs — promoting to main when the target is a finished omnibus. Invoke as /ship # (optionally --onto ). A leaf issue is implemented by one player; an issue with native GitHub sub-issues is an omnibus — fanned out across players…