Loading...
Loading...
Found 3,152 Skills
タスク完了後に自律的に実行する必要があるフロースキルです。 Trigger: task completed, ready to submit code
Update Storybook visual regression snapshots after intentional UI changes. Use when visual tests fail due to expected changes, or when asked to update snapshots.
Show commands and skills that have never been used
Expert knowledge of testing Node.js and Express applications including Jest configuration, Supertest for API testing, unit vs integration vs e2e testing, mocking external APIs, test organization, code coverage, CI/CD integration, and TDD practices. Use when writing tests, setting up testing framework, debugging test failures, or adding test coverage.
Run formatting, lint, typecheck, and tests for this repo; use when validating changes or investigating CI failures.
Create GitHub issues using data-driven templates. Supports any issue type via configurable template configs. Use when the user asks to create a GitHub ticket, issue, or support ticket, or when they want to add a new issue template.
Systematic implementation using APEX methodology (Analyze-Plan-Execute-eXamine) with parallel agents, self-validation, and optional adversarial review. Use when implementing features, fixing bugs, or making code changes that benefit from structured workflow.
Use when jUnit extensions including custom extensions, rules, and conditional test execution.
Run /check-virality, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-virality instead if you want to fix issues immediately.
Main orchestrator for autonomous coding operations. Use when running autonomous sessions, coordinating components, managing the full lifecycle, or orchestrating implementations.
Use when advanced Pytest features including markers, custom assertions, hooks, and coverage configuration.
Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given a bead/issue ID to plan. Triggers on /flow:plan with text descriptions or issue IDs (e.g., bd-123, gno-45, app-12).