kit

Plugin kit from marketplace claude-kit in rranauro/claude-kit. Commands read from the repo's manifest — 6 days ago.

Skills (27)

• argument-pages

  Build a self-contained HTML page that argues one technical position from verified evidence — schema, queries, call sites — for a reviewer to read and act on. Use when a review, design comparison, or schema proposal needs more than terminal scrollback, or when another skill needs the evidence-page fo

• asking-a-human

  The axis for a question a pass puts to a person — the register it is written in, the reach it carries as evidence, and what is not a finding. Use when a pass is about to ask a person to decide — parking the question on an issue, or asking it out loud mid-run — or when another skill needs the reach v

• behavior-placement

  Decide where behavior belongs — model, domain object, or service — and whether the answer already exists. Use when designing new classes, reviewing a proposed service, refactoring, or when another skill needs the placement checks.

• domain-modeling

  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.

• grilling

  Pressure-test a plan, decision, or idea by asserting what is true about it and confirming agreement, raising a decision only where one genuinely exists. Use when the user wants a direction or a ticket's boundary checked before committing to it, or uses any 'grill' trigger phrases.

• improve-codebase-architecture

  Scan a codebase for misshapen objects and present them as a visual HTML report in plans/, ranked strongest to weakest, then file the strongest as tickets under an epic and walk them through triage.

• observations

  Record what a pass learned while running as a checkable claim in a store outside the repo, instead of asking the user about it — the record shape, where the store lives, and the triage that clears it down. Use when a pass closes holding something the ticket did not ask for, or when a command needs t

• park

  Stop an unattended pass at a question only a person can answer — the comment, the kit-blocked label, the worktree left in place, and the report line. Use whenever a command running without a user reaches a decision it may not make.

• project-rules

  Find what a project says about how the kit runs there — which files hold its rules, which one wins when two speak, how a rule in the project's own words overrides a kit default, and where a setting may be recorded. Use whenever a command or skill reads a kit section such as `## Ship gate` or `## Wor

• rails-codebase-design

  The axis for judging object shape in a Rails codebase — what a well-formed class looks like, what to count when one isn't, the structural moves that fix it, and what is not a finding. Use when comparing design approaches, judging a proposed class or extraction, or when another skill needs the object

• rails-excludable-specs

  The axis for judging whether one RSpec example may be left out of a project's default suite run — what makes an example excludable, the evidence rarity and cost each need, what is not a reason, how an excludable example differs from a deletable one, and the tag that excludes it and the runner argume

• rails-load-bearing-specs

  The axis for judging whether one RSpec example is load-bearing — the positive definition, the three categories that convict a deletion candidate and the evidence each needs, and what is not a finding. Use when pruning a spec suite, when judging whether one example earns its place, or when another sk

• reshape

  Reshape the namespaces a shape-held pull request touched, with the person at the hold choosing each move — committed on that PR's branch with no ticket, or filed as a ticket blocked on the issues that PR closes. Use when kit:ticket-loop hand-off holds a PR on shape findings and the person takes the

• shape-review

  Judge the object shape a pull request, or a local diff between a base and a head, introduces — its new classes, signatures and call sites, scored on kit:rails-codebase-design with placement included — as one Markdown comment a person can post as written. Use when a PR's author was an unattended agen

• show-me

  Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.

• start-ticket

  Take a GitHub issue to a wired worktree with its plan verified — the clean-main check, the worktree off the base branch, the gitignored runtime files a fresh worktree lacks, and the qualification test that decides whether the approach is settled. Use when an orchestrator needs a ticket set up for im

• startable-tickets

  Decide which open tickets an agent may pick up unbidden — the candidate query, the five conditions, and the batched lookups that answer them. Use when sweeping a backlog for work to start, or listing what a sweep would take.

• ticket-artifacts

  Where a plan, a design brief, or a walkthrough is stored and how it is found again — one marked comment on the issue as the store, a gitignored local mirror as the cache. Use whenever a command writes or looks for one of those artifacts.

• ticket-loop

  Carry one named ticket from a wired worktree to an open PR — prepare, TDD, simplify, push — attended with gates you answer, or unattended with each gate replaced by a rule and a park where no rule decides. Use when a command has chosen a ticket and needs it implemented.

• to-tickets

  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

• triage-memory

  Audit a project's auto-memory directory, bin every memory as stale, workflow, duplicate/conflicting, or unclassified, and clear it down with the user's per-bin approval. Use when memory has grown large, a memory turns out to be wrong, or the user asks to triage, prune, or audit memory.

• visual-pr

  Write or rewrite a pull request body a reviewer can stop reading after the first section — Gist, acceptance criteria, evidence and screenshots, reviewer instructions, reversibility. Use when writing a PR body, or when asked for the gist of a PR, its core data structure or migration, its blast radius

• visual-review

  Assess someone's pull request for a reviewer in one Gist-first page: the gist, the issue's acceptance criteria rated met/partial/missed, graded evidence, code-shape flags, whether automated reviews were addressed, whether the description matches the code, reversibility, and whether to walk it. Use w

• working-files

  Resolve where the kit keeps a project's working files — the plan cache, the PR scratch notes, the glossary and the ADR directory — from the project's `## Working files` section, and keep a local one out of git without touching a tracked `.gitignore`. Use whenever a command or skill builds one of tho

• worktree-conventions

  Resolve where a project's git worktrees live and how they are created, provisioned, served, and removed — by delegating to the project's own command when it has one, and falling back to a built-in layout when it doesn't. Use whenever a command needs to make, find, or remove a worktree.

• worktree-reclaim

  Reclaim git worktrees and delete their branches safely — one named target or a sweep, attended or unattended. Use when a ticket has merged, when worktrees have accumulated, or when another command needs a worktree torn down.

• writing-tickets

  Draft lean GitHub issues that state the problem and the decision without freezing an implementation. Use when filing an issue or ticket, or when another skill needs the ticket format.

Slash commands (15)

• /kit:architect
• /kit:commit

  Commit the current changes, split by concern, running the project's own test, lint and security gates on what changed. Use when `kit:ticket-loop`, `/kit:new-pull-request`, `/kit:review-copilot` or `/kit:polish-ticket` hands off work to commit.

• /kit:design

  Settle how to build a ticket whose problem is already decided — place the behavior, compare approaches, grill the choice, and store the plan on the issue. Use when `/kit:triage`, `kit:start-ticket` or `kit:ticket-loop` hands off a ticket with no settled approach.

• /kit:list
• /kit:new-pull-request

  Push the current branch and open its pull request, with a Gist-first body wired to the issue. Use when `kit:ticket-loop` hands off an implemented branch to open its PR.

• /kit:observe
• /kit:polish-ticket
• /kit:prune-specs
• /kit:review-copilot

  Collate the automated reviews on a pull request and address each finding against the code, recording every decision. Use when `kit:ticket-loop` or `/kit:start-review` hands off a PR whose reviews have landed, or when a CI gate calls it unattended.

• /kit:ship-ticket
• /kit:start-review
• /kit:triage-memory-run
• /kit:triage
• /kit:walkthrough
• /kit:worktree-gc

  Remove a git worktree and delete its branch where GitHub accounts for the tip. Use when `/kit:start-review`, `kit:start-ticket` or `/kit:polish-ticket` hands off a worktree to reclaim.

Subagents (4)

• reclaim-sweep

  Sweep this project's dead worktrees unattended, isolated from the caller's session, and hand back what was reclaimed and what was held. Use when a command needs the reclaim sweep run without it filling that command's context.

• reshape-inventory

  Gather the evidence a reshape is decided on — the scope, the shape of each namespace in it, and the ranked candidates with their call sites outside the diff — for one shape-held pull request, isolated from the caller's session. Use when kit:reshape step 3 needs its inventory. Pins its own model; lau

• shape-reviewer

  Run kit:shape-review on one pull request, or on the diff between two refs, isolated from the caller's session, and hand back its marked comment. Use when kit:ticket-loop needs a diff's shape judged — before the PR opens, or over what a review round added. Pins its own model; launch it with none.

• spec-assessor

  Apply kit:rails-load-bearing-specs to one spec file, isolated from the caller's session, and hand back that axis's output contract. Use when /kit:prune-specs fans out its per-file assessment. Pins its own model; launch it with none.

Similar plugins