Testing
Unit tests, integration tests, test automation
spec-kit
by ahgraber
Use when work involves Spec Kit and you need to choose the correct spec-kit-* sub-skill, enforce artifact-order gates, or route remediation work (for example sequence violations or specification drift at any stage).
spec-kit-tasks
by ahgraber
Use when an approved Spec Kit plan.md + spec.md must be decomposed into dependency-ordered tasks.md, or when tasks.md is missing/stale after planning or reconciliation changes.
spec-kit-reconcile
by ahgraber
Use when specification drift is discovered at any stage and existing Spec Kit artifacts (spec.md, plan.md, tasks.md) must be reconciled in-place without creating a new feature branch.
spec-kit-clarify
by ahgraber
Use when an existing Spec Kit spec.md has high-impact ambiguity (for example [NEEDS CLARIFICATION], unresolved scope decisions, or unquantified requirements) that must be resolved before spec-kit-plan.
spec-kit-implement
by ahgraber
Use when approved Spec Kit tasks.md must be executed into implementation changes, or when task execution is blocked by sequencing/checklist gates before feature completion.
spec-kit-analyze
by ahgraber
Use when spec.md, plan.md, and tasks.md exist and you need a read-only Spec Kit audit for consistency, requirement-to-task coverage, ambiguity, duplication, or constitution conflicts before implementation.
python-testing
by ahgraber
Use when writing or reviewing tests for Python behavior, contracts, async lifecycles, or reliability paths. Also use when tests are flaky, coupled to implementation details, missing regression coverage, slow to run, or when unclear what tests a change needs.
spec-kit-constitution
by ahgraber
Use when creating or amending a Spec Kit project constitution, especially when memory/constitution.md is missing, contains [PLACEHOLDER] tokens, or principle changes must be propagated to planning/spec/task templates.
spec-kit-specify
by ahgraber
Use when a Spec Kit feature needs spec.md authored or rewritten from natural-language requirements, especially when the feature has no usable specification or requirements are too vague for planning.
@gw-autonomous-workflow
by mthines
Autonomous feature development workflow using isolated worktrees. Use this skill to autonomously implement features from task description through tested PR delivery. Handles worktree creation, implementation, testing, iteration, documentation, and PR creation. Triggers on requests for autonomous feature development, end-to-end implementation, or "implement X feature autonomously."
feature-workflow-orchestrator
by organvm-iv-taxis
End-to-end feature development orchestration from planning through deployment with quality gates
tdd-workflow
by organvm-iv-taxis
Test-driven development workflow with comprehensive coverage requirements including unit, integration, and E2E tests
browser-verification
by srstomp
Automatically verify UI changes in a real browser after implementation. Integrated into the /work workflow — checks visual elements, interactions, and console errors using Playwright. Not a standalone skill.
testing-patterns
by organvm-iv-taxis
Write effective tests across the stack—unit, integration, E2E, and visual regression. Covers testing philosophy, framework selection, mocking strategies, and CI integration. Triggers on testing, test coverage, TDD, or quality assurance requests.
fullstack-starter-pack
by organvm-iv-taxis
Curated bundle of essential skills for fullstack web development. Installs API design, testing, deployment, backend patterns, frontend architecture, and code quality skills together. Use when starting a new fullstack project or onboarding onto a codebase.
verification-loop
by organvm-iv-taxis
Comprehensive quality verification system for code changes with build, type, lint, test, and security checks
o
by paulonasc
Multi-agent coordination through files. Memory, threads, briefings, handoffs.
solo-review
by fortunto2
Final code review and quality gate — run tests, check coverage, audit security, verify acceptance criteria from spec, and generate ship-ready report. Use when user says "review code", "quality check", "is it ready to ship", "final review", or after /deploy completes. Do NOT use for planning (use /plan) or building (use /build).
vcp-review-tests
by Z-M-Huang
Review test quality against VCP testing standards. Checks for tautological tests, over-mocking, missing edge cases, and other anti-patterns.
vcp-coverage-gaps
by Z-M-Huang
Identify untested code by mapping source files to test files. Finds functions without tests and tests missing edge case coverage.
vcp-test-plan
by Z-M-Huang
Generate a test plan for specific code based on VCP testing standards. Produces unit tests, integration tests, edge cases, and mock guidance.
magento-php-specialist
by maxnorm
Advanced PHP development for Magento 2 following PSR-12 and Magento coding standards. Use when writing PHP code, implementing business logic, or ensuring code quality. Masters modern PHP features, object-oriented programming, design patterns, and Magento-specific PHP practices.
warping
by diegosouzapw
Apply warping framework standards for AI-assisted development. Use when starting projects, writing code, running tests, making commits, or when the user references warping, project standards, or coding guidelines.
sylvadoc
by diegosouzapw
Les préférences de Sylvadoc pour la confection de projets web en Nuxt/Vue/Typescript.