zoolutions/claude-plugins

finish-prs

Drive a set of open PRs to merge-ready, one at a time, in a given order. Use when several open PRs need to land in order, or a stack of PRs based on each other's branches. Reads lode/workflow.md → Conflicts to auto-resolve the recurring mechanical conflicts…

원문 언어: 영어

gate

The pre-PR gate. Run before git push or gh pr create and at the verify phase of any implementation workflow. Fresh-context agents review the branch diff against the repo's rules, its lode and the shared checklists; every new test is proven to fail without the…

원문 언어: 영어

learn

Write accepted review findings back into the repository's lode as current-state rules so the next /lode:gate enforces them, and promote a finding to the shared plugin checklists when it applies to more than one repo. Run after processing PR review comments…

원문 언어: 영어

lfg

The full autonomous engineering workflow, from an empty branch to an open PR. Use when implementing a feature, taking on a GitHub issue, or executing a plan file — understand, explore, plan, TDD, verify, gate, PR, and a comprehension close-out. Not for a…

원문 언어: 영어

review-pr

One full pass over an open pull request — resolve merge conflicts with the base, fix red CI, then answer and resolve every unresolved review comment. Run it when a PR needs a full pass, when CI is red, or when there are review comments to process; pass a…

원문 언어: 영어

seed

Create a repository's lode from scratch and turn on the pre-PR gate; with "workflow", write or refresh lode/workflow.md (the profile the shared /lode:lfg, /lode:review-pr and sibling skills read) from CLAUDE.md, the rules and any local commands, leaving the…

원문 언어: 영어

plan

Design a change before building it. Use for anything non-trivial before /lode:lfg or any implementation session — a feature crossing layers, a change to a persisted format, a fix whose shape is not obvious. Read-only, never edits application code; it…

원문 언어: 영어

sync

Keep the repository's lode true to the code. Use after the user accepts a change ("ship it", "looks good", "this is final"), after any change to behaviour or structure, when asked to "audit the lode", for a session handover, or after a merge that touched…

원문 언어: 영어

debug-flaky

Use when a test looks intermittent — an Actions run that's red where others were green, a PR check that failed and passed on retry, or a locally observed flake. Takes a failed run URL, a PR, or a test path; drives evidence → forced reproduction → root cause →…

원문 언어: 영어

tdd

Use when implementing any feature or fixing any bug. Enforces RED -> GREEN -> REFACTOR: write the failing test first, run it, watch it fail for the right reason, implement the minimum, then refactor with the test still green. Reads the repository's test…

원문 언어: 영어