ratchet

Plugin ratchet from marketplace ratchet in praveenvijayan/Ratchet. Commands read from the repo's manifest — 1 month ago.

Skills (12)

• ratchet-herd

  Operate the ratchet-herd fleet supervisor. Validates `.ratchet/herd.json` and surfaces the init hint when it is missing (starting nothing), starts the supervisor when none is running, or attaches to a running one and summarizes its state — live workers, attempts, and pending escalations. A thin conv

• ratchet-hotfix

  The human-triggered hotfix/revert fast lane for production breakage. Runs only when a human says "hotfix" or "revert PR #M" — never self-invoked on suspicion. Reverts the causal merge with `git revert -m 1` on a fresh `hotfix/<slug>` branch off current main in a worktree (or a minimal forward fix on

• ratchet-init

  One-time setup for a repo adopting the factory. Creates the state:* and priority:* labels, detects the project's stack and fills GATES.md, scaffolds the memory files and generates a coarse codebase map (memory/ARCHITECTURE.md), and ensures the Personal Access Token the issue-flow automation depends

• ratchet-map

  Regenerate memory/ARCHITECTURE.md — a coarse, language-agnostic map of the codebase the agent uses to orient and scope its reads. Use when the structure has drifted enough that incremental updates aren't enough, or to refresh a stale map. Writes the file and stops for review; never commits.

• ratchet-memory

  Curate memory/MEMORY.md — merge duplicate entries, prune obsolete ones, and verify that each entry's linked issue/PR still resolves. Use periodically (e.g. quarterly) or when MEMORY.md grows past ~300 lines. Edits the file and stops for human review; never commits.

• ratchet-metrics

  Report loop health from GitHub data — cycle time (ready→merged), rework rate, stale-claim sweep count, and queue depth by state. Read-only, uses your existing gh auth only, and never mutates an issue, label, file, or anything else. Use to see whether the delivery loop is flowing and where it stalls.

• ratchet-next

  After a human acts on a PR, do the right next thing — locally, no CI, no API key. If the PR was approved and merged, sync main and start the next ready issue. If it was rejected (Request Changes, closed with a comment, or new review comments) or the human gave feedback in chat, rework the same branc

• ratchet-plan

  Turn work into plan/*.md issue files and place them on the rolling planning PR for review. Handles both a quick single report ("/ratchet-plan google signin broken") and a full multi-issue plan from the conversation. Writes files onto the evergreen ratchet/planning branch, pushes, and opens or update

• ratchet-status

  Diagnose the queue and explain why work is or isn't flowing, especially when nothing is state:ready (a "backlog drained" report). Read-only — counts issues by state, finds drafts missing acceptance criteria, traces blocked chains to their root, flags an unmerged planning PR or uncommitted plan files

• ratchet-sync

  Compile plan/*.md into GitHub issues immediately by running scripts/plan-sync.mjs locally. This is the LOCAL / no-PR escape hatch — the normal path is to merge the rolling planning PR (which runs plan-sync on main). Use this only when you are NOT using the planning-PR flow (e.g. an unprotected main,

• ratchet-uninstall

  Cleanly remove Ratchet from this project. Manifest-driven — removes only the framework files recorded in this project's `.ratchet-install.json` (preserving generated files like `GATES.md`/`memory/` and your `plan/*.md` unless you opt in), and offers to clean up the GitHub-side state (labels, secret,

• ratchet-update

  Update Ratchet framework files in this repo to a newer upstream version, on a review branch. Manifest- and profile-aware — pulls only the `framework` files for the profile(s) recorded in this project's `.ratchet-install.json`, never the whole tree, and never project-owned or generated paths (`GATES.