メニュー
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".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | run-tests |
| description | 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". |
| metadata | {"author":"profoundry-us","version":"1.0.0"} |
Runs the LocoMotion or demo RSpec test suite inside the appropriate Docker container and reports results.
| Goal | Command |
|---|---|
| Library unit tests (default) | just loco-test |
| Demo application tests | just demo-test |
| Both suites | Run just loco-test first, then just demo-test |
When in doubt, run both.
Before running anything, verify the target exists:
grep -E '^loco-test|^demo-test' Makefile justfile
Use the exact recipe name from the file.
just loco-test
This executes rspec inside the loco Docker container. Equivalent manual
command:
docker compose exec -it loco bundle exec rspec
just demo-test
Equivalent manual command:
docker compose exec -it demo bundle exec rspec
If tests were run as a prerequisite for committing or deploying, do not continue until all tests pass. Fix the failing code, then rerun the affected suite to confirm.
Example 1 — standard pre-commit check
User: "Run the tests before I commit"
just loco-test
just demo-test
Report: "All 142 examples pass. You are clear to commit."
Example 2 — single spec file
User: "Run just the badge component spec"
docker compose exec -it loco bundle exec rspec spec/components/daisy/data_display/badge_component_spec.rb
Example 3 — run tests after adding a new component
After creating a new component and its spec, run:
just loco-test
If the new spec file is not picked up, verify it is inside spec/components/
and follows the _spec.rb naming pattern.
Container not running — Run docker compose ps to check container status.
Start containers with docker compose up -d.
Bundle errors — Run docker compose exec -it loco bundle install to
install missing gems.
Tests time out — Check for infinite loops or missing database seeds in the failing spec. Run the spec in isolation to confirm.
just loco-test command not found — Check that just is installed and
you are running from the project root. Alternatively use the docker compose exec form directly.
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".