testing-production
Production validation specialist ensuring applications are fully implemented and deployment-ready. Use to verify no mock/stub/fake implementations remain, validate against real databases and APIs, perform end-to-end testing with actual systems, and confirm production readiness.
Best use case
testing-production is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Production validation specialist ensuring applications are fully implemented and deployment-ready. Use to verify no mock/stub/fake implementations remain, validate against real databases and APIs, perform end-to-end testing with actual systems, and confirm production readiness.
Teams using testing-production should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/testing-production/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How testing-production Compares
| Feature / Agent | testing-production | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Production validation specialist ensuring applications are fully implemented and deployment-ready. Use to verify no mock/stub/fake implementations remain, validate against real databases and APIs, perform end-to-end testing with actual systems, and confirm production readiness.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Testing Production ## Quick Start ```bash # Scan for incomplete implementations grep -r "mock\|fake\|stub\|TODO\|FIXME" src/ --exclude-dir=__tests__ # Run production validation tests npm run test:production npm run test:e2e # Validate against real services npm run test:integration -- --env=staging ``` ## When to Use - Before deploying to production - After completing TDD implementation phase - To verify no mock implementations remain in production code - To test against real databases, APIs, and infrastructure - To validate performance under realistic load - To confirm security measures are properly implemented ## Prerequisites - Completed unit/integration test suite - Access to staging environment with real services - Environment variables for real service connections - Load testing tools (if validating performance) ## References - [Continuous Delivery](https://continuousdelivery.com/) - [Testing in Production](https://launchdarkly.com/blog/testing-in-production/) - [OWASP Testing Guide](https://owasp.org/www-project-web-security-testing-guide/) ## Version History - **1.0.0** (2026-01-02): Initial release - converted from production-validator agent ## Sub-Skills - [Configuration](configuration/SKILL.md) - [Example 1: Complete Validation Suite (+2)](example-1-complete-validation-suite/SKILL.md) - [Example 4: Security Validation](example-4-security-validation/SKILL.md) - [Real Data Usage (+3)](real-data-usage/SKILL.md) ## Sub-Skills - [Execution Checklist](execution-checklist/SKILL.md) - [Error Handling](error-handling/SKILL.md) ## Sub-Skills - [Production Validation vs Unit Testing (+1)](production-validation-vs-unit-testing/SKILL.md) - [1. Implementation Completeness Check (+2)](1-implementation-completeness-check/SKILL.md) - [Metrics & Success Criteria](metrics-success-criteria/SKILL.md) - [MCP Tools (+2)](mcp-tools/SKILL.md)
Related Skills
well-production-dashboard
Create interactive well production dashboards with real-time monitoring, verification integration, economic metrics, and multi-format exports. Use for well performance analysis, field aggregation, production forecasting, and API-driven dashboards.
production-forecaster
Forecast oil & gas well production using decline curve analysis. Use when estimating EUR, generating type curves, fitting Arps models (exponential, hyperbolic, harmonic), or running reserve calculations. Supports conventional and unconventional wells, P10/P50/P90 probabilistic outputs, and multi-field type curve comparison.
gtm-site-readiness-audit-local-vs-production
Audit GTM feature work by separating local artifact readiness from production deployment state, then fix common blockers in aceengineer-website and GTM collateral.
webapp-testing
Web application testing toolkit using Playwright with Python. Use for verifying frontend functionality, debugging UI behavior, capturing browser screenshots, viewing browser logs, and automating web interactions.
testing-tdd-london
TDD London School (mockist) specialist for mock-driven, outside-in development. Use for behavior verification testing, contract-driven development, testing object collaborations, or when focusing on HOW objects interact rather than WHAT they contain.
github-actions-2-matrix-builds-for-cross-platform-testing
Sub-skill of github-actions: 2. Matrix Builds for Cross-Platform Testing.
orcaflex-static-debug-incremental-static-testing
Sub-skill of orcaflex-static-debug: Incremental Static Testing (+1).
webapp-testing-wait-for-dynamic-content
Sub-skill of webapp-testing: Wait for Dynamic Content (+5).
webapp-testing-static-html
Sub-skill of webapp-testing: Static HTML (+2).
webapp-testing-start-server-before-testing
Sub-skill of webapp-testing: Start Server Before Testing (+1).
webapp-testing-slow-motion
Sub-skill of webapp-testing: Slow Motion (+3).
webapp-testing-example-1-screenshot-comparison-testing
Sub-skill of webapp-testing: Example 1: Screenshot Comparison Testing (+2).