dev-skills

Plugin dev-skills in eumemic/dev-skills. Commands read from the repo's manifest — 1 month ago.

Skills (11)

• bughunt

  One iteration of hypothesis-driven bug discovery — audit the codebase against project invariants and risk patterns via parallel agents, adversarially verify each candidate, and file a groomed bug-issue (red-test sketch + verification evidence + proposed root-cause fix) for every finding that clears

• build-cycle

  Reference document used by the build-iteration skill /shovel-ready for its single-iteration machinery — branch, sync-with-master, /ship handoff, /retro pass, merge, and declaring the loop outcome. NOT user-invokable, and NOT the loop. The loop lives in `/loop`; this is one iteration's build cycle. T

• file-cycle

  Reference document shared by the find-and-file iteration skills (/kaizen, /bughunt, /kaikaku) for their common single-iteration machinery — author groomed issue(s), label by validation, file autonomously (multi-output), and declare the loop outcome. NOT user-invokable, and NOT the loop. The loop liv

• git-workflow

  This skill should be used when the user asks to "commit", "push", "create a PR", "open a pull request", "monitor CI", "fix CI", "fix the build", "request review", "merge", "merge the PR", or mentions any git-based development workflow operations.

• investigate

  This skill should be used when the user asks to "diagnose", "debug", "investigate", "why is this broken", "find the root cause", "figure out why", "look at the logs", "what's going on", or when the user corrects with "you failed to get to the bottom of it" or questions apparent success. Also use whe

• kaikaku

  Continuous architectural simplification and correctness-by-construction — whole-system recon via parallel agents to find high-leverage opportunities to simplify-and-beautify a structure OR foreclose a whole defect-class by making an illegal state unrepresentable, at the module/layer/concept altitude

• kaizen

  One iteration of accidental-complexity reduction — audit the codebase against craftsmanship principles via parallel agents, and file a groomed cleanup-issue for every candidate that clears the gate. Does NOT implement or ship — specialized dev processes pick up the filed issues. Use when invoked as

• loop

  Drive any single-iteration development skill as an autonomous loop — invoke one iteration, read its declared outcome, then pace, escalate, or stop. Use when invoked as `/loop <skill> [flags]` (e.g. `/loop kaizen --auto`, `/loop bughunt`, `/loop kaikaku`, `/loop shovel-ready --auto`). Owns cadence, i

• retro

  Reflect on a slice of the current session (a single iteration, the whole session, or a natural pause point) to identify durable, codifiable learnings about workflow OR dev infrastructure — and ship them only if they clear a quality bar. Most invocations produce nothing; that's the point. Use when th

• ship

  Drive a code change from working tree to a green PR — runs project checks, /simplify, code-review subagent, commits, opens PR, monitors CI. Stops when CI is green; caller handles merge. Use when invoked as `/ship`, or when `/shovel-ready` hands off a working tree of changes to be shipped. Project-ag

• shovel-ready

  One iteration against a GitHub `shovel-ready` issue queue — if non-empty, take the highest-ROI issue (TDD, /ship, /retro, merge); if empty, audit closed work and unlabeled candidates to refill it; declare the outcome. Use when the user invokes `/shovel-ready`, asks to "work the shovel-ready queue",

Similar plugins