loco_motion

Generates a pull request description from commit history, updates the CHANGELOG, and opens the PR on GitHub. Use when the user says "create a PR", "open a pull request", "make a PR", "submit a PR", or "create a pull request".

Investigates a problem, then writes and posts a well-structured GitHub issue. Use when the user says "create an issue", "open an issue", "file an issue", "report this bug", or "write a GitHub issue".

Boots the LocoMotion demo Rails app, serving it on port 3000. Uses Docker locally (via `just demo`) and a no-Docker rbenv/node fallback for cloud sessions. Use when the user says "run the app", "start the demo", "boot the server", or as a prerequisite before taking screenshots or videos.

Adds entries to CHANGELOG.md under the correct section following Keep-a-Changelog conventions. Use when the user says "update the changelog", "add a changelog entry", "update changelog", or "log this change".

Reads a GitHub issue, crafts a branch name, and optionally creates an implementation plan. Use when the user says "start this issue", "work on issue", "begin issue", "pick up issue", or "let's work on".

Takes a full-page screenshot or video of a LocoMotion demo page using Playwright. Requires the demo server to already be running (see the run-demo skill). Use when the user says "screenshot", "take a screenshot", "show me what it looks like", "capture the page", or "record a video".

Reviews staged or recent code changes against LocoMotion coding conventions and Windsurf rules before committing. Use when the user says "check my code", "review my changes", "lint my code", "does this follow conventions", or "code check".

Stages all changes, writes a well-structured Markdown commit message, commits, and pushes to the remote branch. Use when the user says "commit", "commit and push", "push my changes", "save my work", or "ship this".

Creates a structured Markdown implementation plan in docs/plans/ using the appropriate template. Use when the user says "create a plan", "make a plan", "plan this out", "write a plan for", or "draft an implementation plan".

Adds or improves YARD documentation for a LocoMotion component class and its initialize method. Use when the user says "document a component", "add YARD docs", "write the docs", "document this component", or "add documentation".

Modifies an existing LocoMotion DaisyUI ViewComponent — adding parts, slots, CSS tweaks, or behavioral changes — while keeping all related files in sync. Use when the user says "update a component", "modify a component", "add a part to", "change the component", or "fix a component".

Creates all stub files for a new LocoMotion DaisyUI ViewComponent. Generates the component class, HAML template, RSpec spec, demo example view, and registers the component in helpers.rb. Use when the user says "create a new component", "add a component", "scaffold a component", or "new component workflow".

Writes and runs Playwright end-to-end tests for LocoMotion demo pages inside the Docker demo container. Use when the user says "write playwright tests", "add e2e tests", "run playwright", "write e2e tests", or "test with playwright".

Runs the LocoMotion RSpec test suite inside the correct Docker container. Use when the user says "run tests", "run the test suite", "check tests", "just loco-test", "just demo-test", or "run specs".