Senior Qa
Design test strategy, scaffold unit and E2E suites, and analyze coverage for React, Next.js, and Node apps before release.
Overview
Senior Qa is an agent skill most often used in Ship (also Build) that designs QA strategy and scaffolds test automation and coverage analysis for React, Next.js, and Node applications.
Install
npx skills add https://github.com/davila7/claude-code-templates --skill senior-qaWhat is this skill?
- Three Python tooling paths: test suite generator, coverage analyzer, and E2E test scaffolder
- Oriented to ReactJS, NextJS, and NodeJS stacks with configurable templates and built-in quality checks
- Coverage analyzer surfaces performance metrics, recommendations, and optional automated fix suggestions
- E2E scaffolder provides expert-level scaffolding for end-to-end automation setup
- Supports manual testing workflows and test-case authoring alongside automation
- 3 core Python automation scripts: test suite generator, coverage analyzer, E2E test scaffolder
Adoption & trust: 895 installs on skills.sh; 27.8k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are shipping a JS full-stack app but lack a structured test plan, automated suites, or visibility into what your coverage actually protects.
Who is it for?
Solo builders on React/Next/Node who want agent help turning vague “we should test this” into suites, coverage reports, and E2E structure before launch.
Skip if: Teams that only need production incident debugging, non-JS stacks with no React/Next/Node surface, or shops that already enforce a mature CI matrix and only want flake triage.
When should I use this skill?
Designing test strategies, writing test cases, implementing test automation, performing manual testing, or analyzing test coverage for ReactJS, NextJS, NodeJS applications.
What do I get? / Deliverables
You get generated test scaffolding, analyzed coverage with actionable gaps, and E2E setup guidance so you can gate releases with evidence instead of ad-hoc manual clicks.
- Generated test suite scaffolding
- Coverage analysis report with recommendations
- E2E test harness starter structure
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship because the skill’s stated triggers are test strategy, automation, manual QA, and coverage analysis—the work you do when hardening software for release. Testing is the subphase where suite design, E2E setup, and coverage gates belong; the bundled Python scripts directly support those ship-phase deliverables.
Where it fits
Scaffold component and page tests while iterating on a Next.js UI before merge.
Generate API route test templates and coverage targets for a Node service.
Run coverage analysis and expand E2E flows ahead of a production deploy.
Use quality metrics and recommendations to justify what must pass before tagging a release.
How it compares
Use as a skill-driven QA playbook with Python scaffolders—not as a hosted test runner or a single-purpose linter integration.
Common Questions / FAQ
Who is senior-qa for?
Indie and solo developers building React, Next.js, or Node products who need test strategy, case design, automation setup, and coverage analysis without hiring a dedicated QA lead.
When should I use senior-qa?
During Build when you add features and want tests co-located with frontend or backend work; during Ship when you finalize regression suites, run coverage analysis, scaffold E2E flows, or plan manual test passes before release.
Is senior-qa safe to install?
It includes local Python scripts that read project paths—review the Security Audits panel on this Prism page and inspect script behavior in your repo before running against production secrets or live environments.
SKILL.md
READMESKILL.md - Senior Qa
# Senior Qa Complete toolkit for senior qa with modern tools and best practices. ## Quick Start ### Main Capabilities This skill provides three core capabilities through automated scripts: ```bash # Script 1: Test Suite Generator python scripts/test_suite_generator.py [options] # Script 2: Coverage Analyzer python scripts/coverage_analyzer.py [options] # Script 3: E2E Test Scaffolder python scripts/e2e_test_scaffolder.py [options] ``` ## Core Capabilities ### 1. Test Suite Generator Automated tool for test suite generator tasks. **Features:** - Automated scaffolding - Best practices built-in - Configurable templates - Quality checks **Usage:** ```bash python scripts/test_suite_generator.py <project-path> [options] ``` ### 2. Coverage Analyzer Comprehensive analysis and optimization tool. **Features:** - Deep analysis - Performance metrics - Recommendations - Automated fixes **Usage:** ```bash python scripts/coverage_analyzer.py <target-path> [--verbose] ``` ### 3. E2E Test Scaffolder Advanced tooling for specialized tasks. **Features:** - Expert-level automation - Custom configurations - Integration ready - Production-grade output **Usage:** ```bash python scripts/e2e_test_scaffolder.py [arguments] [options] ``` ## Reference Documentation ### Testing Strategies Comprehensive guide available in `references/testing_strategies.md`: - Detailed patterns and practices - Code examples - Best practices - Anti-patterns to avoid - Real-world scenarios ### Test Automation Patterns Complete workflow documentation in `references/test_automation_patterns.md`: - Step-by-step processes - Optimization strategies - Tool integrations - Performance tuning - Troubleshooting guide ### Qa Best Practices Technical reference guide in `references/qa_best_practices.md`: - Technology stack details - Configuration examples - Integration patterns - Security considerations - Scalability guidelines ## Tech Stack **Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin **Frontend:** React, Next.js, React Native, Flutter **Backend:** Node.js, Express, GraphQL, REST APIs **Database:** PostgreSQL, Prisma, NeonDB, Supabase **DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI **Cloud:** AWS, GCP, Azure ## Development Workflow ### 1. Setup and Configuration ```bash # Install dependencies npm install # or pip install -r requirements.txt # Configure environment cp .env.example .env ``` ### 2. Run Quality Checks ```bash # Use the analyzer script python scripts/coverage_analyzer.py . # Review recommendations # Apply fixes ``` ### 3. Implement Best Practices Follow the patterns and practices documented in: - `references/testing_strategies.md` - `references/test_automation_patterns.md` - `references/qa_best_practices.md` ## Best Practices Summary ### Code Quality - Follow established patterns - Write comprehensive tests - Document decisions - Review regularly ### Performance - Measure before optimizing - Use appropriate caching - Optimize critical paths - Monitor in production ### Security - Validate all inputs - Use parameterized queries - Implement proper authentication - Keep dependencies updated ### Maintainability - Write clear code - Use consistent naming - Add helpful comments - Keep it simple ## Common Commands ```bash # Development npm run dev npm run build npm run test npm run lint # Analysis python scripts/coverage_analyzer.py . python scripts/e2e_test_scaffolder.py --analyze # Deployment docker build -t app:latest . docker-compose up -d kubectl apply -f k8s/ ``` ## Troubleshooting ##