From antigravity-awesome-skills
Orchestrates testing/QA workflow for unit (Jest/Vitest/pytest), integration, E2E (Playwright), browser automation, and quality gates. Use for infrastructure setup, test writing, CI integration.
npx claudepluginhub sickn33/antigravity-awesome-skillsThis skill uses the workspace's default tool permissions.
Comprehensive testing and quality assurance workflow covering unit tests, integration tests, E2E tests, browser automation, and quality gates for production-ready software.
Orchestrates testing/QA workflow for unit (Jest/Vitest/pytest), integration, E2E (Playwright), browser automation, and quality gates. Use for infrastructure setup, test writing, CI integration.
Writes and reviews unit, integration, and E2E tests using Jest, Vitest, Playwright. Validates regression, reviews coverage, configures QA strategies before release.
Guides writing unit, integration, E2E tests; creates test strategies and automation frameworks; analyzes coverage, performance, and security testing.
Share bugs, ideas, or general feedback.
Comprehensive testing and quality assurance workflow covering unit tests, integration tests, E2E tests, browser automation, and quality gates for production-ready software.
Use this workflow when:
test-automator - Test automationtest-driven-development - TDDUse @test-automator to design testing strategy
Use @test-driven-development to implement TDD workflow
javascript-testing-patterns - Jest/Vitestpython-testing-patterns - pytestunit-testing-test-generate - Test generationtdd-orchestrator - TDD orchestrationUse @javascript-testing-patterns to write Jest tests
Use @python-testing-patterns to write pytest tests
Use @unit-testing-test-generate to generate unit tests
api-testing-observability-api-mock - API testinge2e-testing-patterns - Integration patternsUse @api-testing-observability-api-mock to test APIs
playwright-skill - Playwright testinge2e-testing-patterns - E2E patternswebapp-testing - Web app testingUse @playwright-skill to create E2E tests
Use @e2e-testing-patterns to design E2E strategy
browser-automation - Browser automationwebapp-testing - Browser testingscreenshots - Screenshot automationUse @browser-automation to automate browser tasks
Use @screenshots to capture marketing screenshots
performance-engineer - Performance engineeringperformance-profiling - Performance profilingweb-performance-optimization - Web performanceUse @performance-engineer to test application performance
code-reviewer - AI code reviewcode-review-excellence - Review best practicesfind-bugs - Bug detectionsecurity-scanning-security-sast - Security scanningUse @code-reviewer to review pull requests
Use @find-bugs to detect bugs in code
lint-and-validate - Lintingverification-before-completion - VerificationUse @lint-and-validate to check code quality
Use @verification-before-completion to verify changes
/ / \ E2E Tests (10%)
/---- / \ Integration Tests (20%)
/-------- / \ Unit Tests (70%)
/------------```
## Quality Gates Checklist
- [ ] Unit test coverage > 80%
- [ ] All tests passing
- [ ] E2E tests for critical paths
- [ ] Performance benchmarks met
- [ ] Security scan passed
- [ ] Code review approved
- [ ] Linting clean
## Related Workflow Bundles
- `development` - Development workflow
- `security-audit` - Security testing
- `cloud-devops` - CI/CD integration
- `ai-ml` - AI testing
## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.