test
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
- Check git status to identify changed files
- Determine appropriate test scope:
- Keychain changes →
pnpm test - Component/UI changes →
pnpm test:storybook - Example app changes → Test specific example
- Keychain changes →
More from cartridge-gg/controller
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
42codegen
Regenerate GraphQL types from API schema. Use when API schema has changed, GraphQL queries/mutations added or modified, or type errors in API calls.
39validate-before-merge
Run full validation to ensure code is ready for merge. Use before merging PRs, when asked to validate readiness, or as a final check before requesting review.
35update-storybook-snapshots
Update Storybook visual regression snapshots after intentional UI changes. Use when visual tests fail due to expected changes, or when asked to update snapshots.
35pre-commit-check
Run all pre-commit checks before committing changes. Use to manually verify changes pass all quality gates before committing.
34find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
33