orchraft

Plugin orchraft from marketplace orchraft in karloows/orchraft. Commands read from the repo's manifest — 9 days ago.

Skills (18)

• chronicle

  Have the AI draft or update a standalone Markdown doc — a feature write-up, design doc, or a section of README/ROADMAP — grounded in the real diff, code, commit history, or PR/issue text. Use when the user says chronicle, asks to write documentation, draft a design doc, or update a named doc file su

• forgehand

  Have the AI implement a requested code change and run focused validation without committing, pushing, or changing GitHub. Use when the user asks to fix, build, refactor, or test code.

• herald

  Have the AI draft release notes for a tag or the unreleased work since the last one, grounded in the pull requests and commits that actually landed, then write them into the GitHub release once the user approves. Use when the user says herald, asks for release notes, or wants a release described.

• land

  Have the AI finish a topic branch end to end by merging its PR, removing the branch, and syncing the local base branch. Use when the user says land or asks to run the repo landing workflow.

• lore

  Have the AI add or fix code comments and docstrings across a diff or file so they match this repo's lore policy, in whatever language or framework it's written in. Use when the user says lore, asks to comment the code, add docstrings, document a function, or clean up stale/noisy comments.

• muster

  Have the AI report actionable open-PR state across every repo the connected GitHub account owns — failing/pending checks, merge conflicts, unresolved review threads — grounded in live data, not one repo at a time. Use when the user says muster, asks for a portfolio status, wants to know what's actio

• plunder

  Have the AI report this repo's real shipping signal — PRs opened, review findings `roast` caught and whether they were fixed or declined, and time-to-land — grounded in live git/GitHub history, not an invented score. Use when the user says plunder, asks for shipping stats, wants a retrospective on P

• quest

  Have the AI triage, create, or update a GitHub issue before implementation starts. Use when the user says quest, asks to file a bug, create an issue, triage a report, or update an issue's status, labels, or body.

• reckoning

  Have the AI list every review finding that was consciously declined rather than fixed, across the whole repo's pull requests, grounded in live GitHub data. Use when the user says reckoning, asks what's been declined, wants a debt list, or wants to see deferred findings before a release.

• roast

  Have the AI review the current pull request's diff against the target repository's own policies and commit history — not an external ruleset — then post the findings as a PR review with inline comments and a summary. Use when the user says roast, review, asks for a PR review, or wants CodeRabbit-sty

• runes

  Have the AI summarize where the current branch's work actually stands — its PR, checks, and unresolved review findings — grounded in live git/GitHub state, not memory. Use when the user says runes, asks to resume, "where were we", "what's the status", or wants to pick a branch back up without re-exp

• shaman

  Have the AI run a read-only orchraft setup preflight. Use when the user says shaman, asks whether orchraft is ready, or wants a preflight before another workflow.

• ship

  Have the AI branch, commit, push, and create or update a pull request in the current repository. Use when the user says ship, asks to prepare a branch or commit, or wants help following the repo branch and PR workflow without pushing to the base branch.

• warchief

  Have the AI choose the next orchraft lifecycle step and hand off to the right skill, without performing git or GitHub mutations. Use when the user says warchief, asks what should happen next, or wants orchraft to route the work.

• warpath

  Run the fix, ship, and roast cycle for an open pull request until the latest roast reports zero findings. Use when the user asks to repeat review fixes until clean or run the review loop.

• warplan

  Have the AI draft an implementation plan grounded in this repo's own conventions, policies, and precedent before code gets written. Use when the user says warplan, asks to plan a feature or fix, wants a design pass before implementation, or asks how to approach a change.

• watchtower

  Have the AI surface a short read-only status nudge about open PR work without mutating git or GitHub. Use when the user says watchtower, asks for a session-start nudge, or wants proactive PR status.

• yap

  Have the AI explain something — a PR/diff, a file or module, an error or log, a repo policy, or a dependency/changelog — grounded in real sources (code, git history, docs, policies) with citations, not a confident guess. Use when the user says yap, asks "explain this", "why does this exist", "what c

Subagents (8)

• chronicler

  Drafts or updates README, ROADMAP, design, and other standalone Markdown documents from verified repository sources.

• forgehand

  Implements requested code changes while preserving project conventions. Use for coding, debugging, and tests; never for committing, pushing, or opening a pull request.

• loremaster

  Adds or repairs comments and docstrings while preserving code behavior. Edits files only; never ships work.

• rune-reader

  Reports the live branch, pull request, checks, and review state without changing anything.

• scout

  Explains repository code, diffs, errors, policies, and dependencies from real sources. Read-only.

• tactician

  Drafts grounded implementation plans from repository conventions and precedent. Read-only; use before non-trivial code changes.

• trialmaster

  Reviews code and pull requests against the repository's policies and reports actionable findings without posting a review.

• warpath

  Orchestrates fix, ship, and roast cycles until the latest pull-request review is clean; approval-sensitive and never merges.

Hooks (2)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT:-$CLAUDE_PROJECT_DIR}"/hooks/watchtower-nudge.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT:-$CLAUDE_PROJECT_DIR}"/hooks/main-commit-nudge.sh

Similar plugins