meganemura
- 10 skills
- 0 followers
- yesterday last updated
- ▌ Bulldogger · meganemura bundleUse bulldogger failure evidence and re-execution verbs to inspect Ruby runtime behavior or verify a code change.
- ▌ Holdfast · meganemuraRun what you suspect instead of leaving it "read only". In a Ruby or Rails app, write each suspicion (a bug, a race, an effect on another area) as a few lines of YAML; `holdfast check` builds the world with the app's factories, runs it on base and head, and answers confirmed (with a failing spec to keep), refuted (with what it saw), or could_not_run (with the exact error). `holdfast run` checks a change against base, and hunts when nothing changed. Use after reading code, before calling a change safe, or when asked to find bugs.
- ▌ Quint Driver · meganemuraquintdriver runs a Ruby system the way a Quint spec says and compares the two after every step. You write the spec and a driver. Quint or Hegel chooses the steps. A disagreement raises QuintDriver::Mismatch with the steps that reproduce it.
- ▌ Jitcatch · meganemuraUse when reviewing or landing a code change and you want throwaway tests that catch regressions it introduces. Drives the jitcatch CLI (context, run, assess) for a Ruby diff. Write Minitest or RSpec files that pass on the base revision and fail on head, drop flakes, then judge each reported failure as a likely regression or an intended change. The tool never calls a model.
- ▌ Nukadoko Verification · meganemuraUse when a project has, or is getting, a verification skill (a control CLI that drives the running app, plus a feature map of what the app does and how a user reaches it) and its claims need evidence that can be run again; when a bug report has to be reproduced before it is fixed; or when prototypes or the steps of a plan need one yardstick fixed before they are built. Adds nukadoko scenarios as the proof layer under the map. It does not replace the control CLI or the map.
- ▌ Nukadoko · meganemura bundleUse when turning a requirement into a Gherkin scenario and the run that is its evidence, for a person to review, starting from whatever is on hand, whether that is raw prose with no stated acceptance criteria yet (a ticket, a request, a conversation), acceptance criteria that still need concrete scenarios, a scenario ready to write, a path already explored one `nuka do` call at a time and now worth fixing in a scenario, a browser app whose state cannot be repeated and has to be explored through a Playwright MCP server first, or a scenario a person wants to walk one step at a time, the run paused after each step while the agent explains its record and waits for the person's answer.
- ▌ Workflow · meganemuraDrive a headsign phase-gate workflow. Use when the repository has a .headsign/ directory holding one or more workflow files — workflow.yaml, or named ones like fitness.yaml run with `headsign start fitness` — and the user asks to start, continue, or resume a run, or when .headsign/state.json shows a run in progress (e.g. when recovering after compaction). Do not use in repositories that have no .headsign directory.
- ▌ Design Workflow · meganemura bundleDesign and write a headsign workflow file — the YAML that names a repository's phases and holds the shell checks that gate them. Use when the user asks to create a workflow for this repository, to add another one alongside ones already there, or to change how an existing one's phases, gates, routes, or limits are shaped. This skill authors the file and stops at it; starting, continuing, or resuming a run is the `workflow` skill's job instead. The two divide by what is being asked for — writing the graph versus walking it — not by what is on disk, so this one applies whether or not the repository already has a .headsign/ directory.
- ▌ Migration · meganemuraUse when moving an existing test suite onto nukadoko, whether from cucumber-js (typically driving Playwright), from a Playwright Test suite with no cucumber and no Gherkin, or from another DSL already shaped as typed steps. Covers the two-stage discipline that keeps every failure traceable to one change, the `nukadoko/compat` door, sharing an implementation with a Playwright Test suite, and promoting steps to typed `defineStep`s at your own pace.
- ▌ Acceptance · meganemura bundleUse when turning a requirement into a signed-off Gherkin scenario, starting from whatever is on hand, whether that is raw prose with no stated acceptance criteria yet (a ticket, a request, a conversation), acceptance criteria that still need concrete scenarios, a scenario ready to write, or a path already explored one `nuka do` call at a time and now worth fixing in a scenario.