Loading...
Loading...
Found 67 Skills
Full GitHub issue lifecycle: pick an issue, create it, branch, commit, squash, push, PR, merge. Owns every git and gh write in the pipeline. Handles project board integration, base branch detection (main/master/epic-*), and compact step reports. Supports entering at any step.
Implement a GitHub issue or the work agreed in the conversation, check it, and open a pull request that is ready for review.
Use when performing a first-pass, read-only PR review in a clean isolated context.
Inkblot git branch naming convention. Use when creating a branch, checking out a feature/bugfix branch, naming a PR branch, or when the user asks to start work on a Jira ticket.
Use when a finalized non-[DRAFT] GitHub issue needs an implementation plan published for execution in a separate fresh context. Not for refining the specification or for a one-file, one-behavior change.
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks the linked issue, required tests and docs, then writes Description / Proofs / Fixes.