Test
- 34 installs
- 80 repo stars
- Updated July 29, 2026
- cartridge-gg/controller
Run the appropriate test suite (unit, storybook, integration) based on which files changed in the Cartridge monorepo.
About
Runs the appropriate Cartridge test suite based on the type of changed files or the user request. A developer uses it to run the right tests intelligently rather than the full suite.
- Selects test scope based on which files changed
- Routes UI changes to storybook and code changes to unit tests
Test by the numbers
- 34 all-time installs (skills.sh)
- Ranked #1,325 of 2,155 Testing & QA skills by installs in the Skillselion catalog
- Data as of Jul 30, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cartridge-gg/controller --skill testAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 34 |
|---|---|
| repo stars | ★ 80 |
| Last updated | July 29, 2026 |
| Repository | cartridge-gg/controller ↗ |
What it does
Run the appropriate test suite (unit, storybook, integration) based on which files changed in the Cartridge monorepo.
Files
Test Skill
Run appropriate test suites based on changed files or user request.
Usage
Run tests intelligently:
- Unit tests for code changes
- Storybook visual regression for component changes
- Integration tests for example apps
- Full test suite before release
Steps
1. Check git status to identify changed files 2. Determine appropriate test scope:
- Keychain changes →
pnpm test - Component/UI changes →
pnpm test:storybook - Example app changes → Test specific example
- Controller SDK changes → Controller tests + integration
3. Run selected test suite 4. Report results and any failures 5. If visual regressions detected, inform about pnpm test:storybook:update
Notes
- E2E tests currently disabled in CI but can run locally
- Storybook snapshot updates require Docker setup
- Pre-commit hooks automatically run linting/formatting
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3k