Testing
Unit tests, integration tests, test automation
tdd
by citypaul
Test-Driven Development workflow. Use for ALL code changes - features, bug fixes, refactoring. TDD is non-negotiable.
test-design-reviewer
by citypaul
Evaluates test quality using Dave Farley's 8 properties. Use when reviewing tests, assessing test suite quality, or analyzing test effectiveness against TDD best practices.
fact-check
by leonardomso
Verify technical accuracy of JavaScript concept pages by checking code examples, MDN/ECMAScript compliance, and external resources to prevent misinformation
concept-workflow
by leonardomso
End-to-end workflow for creating complete JavaScript concept documentation, orchestrating all skills from research to final review
concept-workflow
by leonardomso
End-to-end workflow for creating complete JavaScript concept documentation, orchestrating all skills from research to final review
test-writer
by leonardomso
Generate comprehensive Vitest tests for code examples in JavaScript concept documentation pages, following project conventions and referencing source lines
test-writer
by leonardomso
Generate comprehensive Vitest tests for code examples in JavaScript concept documentation pages, following project conventions and referencing source lines
fact-check
by leonardomso
Verify technical accuracy of JavaScript concept pages by checking code examples, MDN/ECMAScript compliance, and external resources to prevent misinformation
Forge
by simota
ããã³ãã¨ã³ãï¼UIã³ã³ãã¼ãã³ã/ãã¼ã¸ï¼ã¨ããã¯ã¨ã³ãï¼APIã¢ãã¯/ç°¡æãµã¼ãã¼ï¼ä¸¡é¢ã®ãããã¿ã¤ããç´ æ©ãæ§ç¯ãæ°æ©è½ã®æ¤è¨¼ãã¢ã¤ãã¢ãå½¢ã«ãããæã«ä½¿ç¨ãå®ç§ããåããã®ãåªå ã
testing-best-practices
by NeverSight
Test layering, execution, and CI guidance across unit, integration, and e2e. Use when designing tests, writing test cases, or planning test strategy for a module.
pr-prep
by boshu2
'PR preparation: git archaeology, test validation, structured PR body generation. Mandatory user review gate before submission. Triggers: "prepare PR", "PR prep", "submit PR", "create PR body", "write PR description".'
implement
by boshu2
'Execute a single issue with full lifecycle. Triggers: "implement", "work on task", "build this", "start feature", "pick up next issue", "work on issue".'
pre-mortem
by boshu2
'Validate a plan or spec before implementation using multi-model council. Answer: Is this good enough to implement? Triggers: "pre-mortem", "validate plan", "validate spec", "is this ready".'
plan
by boshu2
'Epic decomposition into trackable issues. Triggers: "create a plan", "plan implementation", "break down into tasks", "decompose into features", "create beads issues from research", "what issues should we create", "plan out the work".'
doc
by boshu2
'This skill should be used when the user asks to "generate documentation", "validate docs", "check doc coverage", "find missing docs", "create code-map", "sync documentation", "update docs", or needs guidance on documentation generation and validation for any repository type. Triggers: doc, documentation, code-map, doc coverage, validate docs.'
crank
by boshu2
'Hands-free epic execution. Runs until ALL children are CLOSED. Local mode uses /swarm with runtime-native spawning (Codex sub-agents or Claude teams). Distributed mode uses /swarm --mode=distributed (tmux + Agent Mail) for persistence and coordination. NO human prompts, NO stopping. Triggers: "crank", "run epic", "execute epic", "run all tasks", "hands-free execution", "crank it".'
dart-test
by dartsim
DART testing patterns - unit tests, integration tests, CI validation
dart-ci
by dartsim
DART CI/CD troubleshooting - GitHub Actions, cache debugging, platform-specific failures
dart-python
by dartsim
DART Python bindings (dartpy) - nanobind, wheel building, API patterns
dart-build
by dartsim
DART build system knowledge - CMake, pixi, dependencies, troubleshooting
technology-stack
by ag-grid
'Technology stack and architectural constraints. Use when choosing technologies, adding dependencies, or understanding zero-dependency requirements.'
estimate-jira
by ag-grid
Estimate complexity, effort, and risks for JIRA tickets, features, or projects. Generates structured reports with time estimates, dependencies, risk analysis, and known unknowns. Use when user asks to "estimate", "size", or "analyze complexity" of work items.
bdd-with-approvals
by lexler
Scannable BDD tests written in domain language. Use when doing BDD.
hexagonal-architecture
by lexler
Applies hexagonal (ports & adapters) architecture. Use when designing application structure, separating domain from infrastructure, creating testable boundaries, or when user mentions ports, adapters, hexagonal, or clean architecture.