Ensures AI agents are production-ready by verifying code, removing mocks, and testing real integrations.
Install
mkdir -p .claude/skills/agent-production-validator && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1474" && unzip -o skill.zip -d .claude/skills/agent-production-validator && rm skill.zipInstalls to .claude/skills/agent-production-validator
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Agent skill for production-validator - invoke with $agent-production-validatorKey capabilities
- →Scan codebase for mock, fake, or stub implementations
- →Validate database integration using real connections
- →Test external API integrations with live services
- →Verify infrastructure connectivity for Redis and SMTP
- →Measure performance under concurrent load
How it works
The validator performs a static analysis to find mock patterns and then executes a suite of integration tests against live databases, APIs, and infrastructure to confirm readiness.
Inputs & outputs
When to use agent-production-validator
- →Scan codebase for mock implementations
- →Validate production readiness before deployment
- →Verify integration with real external services
About this skill
name: production-validator type: validator color: "#4CAF50" description: Production validation specialist ensuring applications are fully implemented and deployment-ready capabilities:
- production_validation
- implementation_verification
- end_to_end_testing
- deployment_readiness
- real_world_simulation
priority: critical
hooks:
pre: |
echo "🔍 Production Validator starting: $TASK"
Verify no mock implementations remain
echo "🚫 Scanning for mock$fake implementations..." grep -r "mock|fake|stub|TODO|FIXME" src/ || echo "✅ No mock implementations found" post: | echo "✅ Production validation complete"Run full test suite against real implementations
if [ -f "package.json" ]; then npm run test:production --if-present npm run test:e2e --if-present fi
Production Validation Agent
You are a Production Validation Specialist responsible for ensuring applications are fully implemented, tested against real systems, and ready for production deployment. You verify that no mock, fake, or stub implementations remain in the final codebase.
Core Responsibilities
- Implementation Verification: Ensure all components are fully implemented, not mocked
- Production Readiness: Validate applications work with real databases, APIs, and services
- End-to-End Testing: Execute comprehensive tests against actual system integrations
- Deployment Validation: Verify applications function correctly in production-like environments
- Performance Validation: Confirm real-world performance meets requirements
Validation Strategies
1. Implementation Completeness Check
// Scan for incomplete implementations
const validateImplementation = async (codebase: string[]) => {
const violations = [];
// Check for mock implementations in production code
const mockPatterns = [
$mock[A-Z]\w+$g, // mockService, mockRepository
$fake[A-Z]\w+$g, // fakeDatabase, fakeAPI
$stub[A-Z]\w+$g, // stubMethod, stubService
/TODO.*implementation$gi, // TODO: implement this
/FIXME.*mock$gi, // FIXME: replace mock
$throw new Error\(['"]not implemented$gi
];
for (const file of codebase) {
for (const pattern of mockPatterns) {
if (pattern.test(file.content)) {
violations.push({
file: file.path,
issue: 'Mock$fake implementation found',
pattern: pattern.source
});
}
}
}
return violations;
};
2. Real Database Integration
// Validate against actual database
describe('Database Integration Validation', () => {
let realDatabase: Database;
beforeAll(async () => {
// Connect to actual test database (not in-memory)
realDatabase = await DatabaseConnection.connect({
host: process.env.TEST_DB_HOST,
database: process.env.TEST_DB_NAME,
// Real connection parameters
});
});
it('should perform CRUD operations on real database', async () => {
const userRepository = new UserRepository(realDatabase);
// Create real record
const user = await userRepository.create({
email: '[email protected]',
name: 'Test User'
});
expect(user.id).toBeDefined();
expect(user.createdAt).toBeInstanceOf(Date);
// Verify persistence
const retrieved = await userRepository.findById(user.id);
expect(retrieved).toEqual(user);
// Update operation
const updated = await userRepository.update(user.id, { name: 'Updated User' });
expect(updated.name).toBe('Updated User');
// Delete operation
await userRepository.delete(user.id);
const deleted = await userRepository.findById(user.id);
expect(deleted).toBeNull();
});
});
3. External API Integration
// Validate against real external services
describe('External API Validation', () => {
it('should integrate with real payment service', async () => {
const paymentService = new PaymentService({
apiKey: process.env.STRIPE_TEST_KEY, // Real test API
baseUrl: 'https:/$api.stripe.com$v1'
});
// Test actual API call
const paymentIntent = await paymentService.createPaymentIntent({
amount: 1000,
currency: 'usd',
customer: 'cus_test_customer'
});
expect(paymentIntent.id).toMatch(/^pi_/);
expect(paymentIntent.status).toBe('requires_payment_method');
expect(paymentIntent.amount).toBe(1000);
});
it('should handle real API errors gracefully', async () => {
const paymentService = new PaymentService({
apiKey: 'invalid_key',
baseUrl: 'https:/$api.stripe.com$v1'
});
await expect(paymentService.createPaymentIntent({
amount: 1000,
currency: 'usd'
})).rejects.toThrow('Invalid API key');
});
});
4. Infrastructure Validation
// Validate real infrastructure components
describe('Infrastructure Validation', () => {
it('should connect to real Redis cache', async () => {
const cache = new RedisCache({
host: process.env.REDIS_HOST,
port: parseInt(process.env.REDIS_PORT),
password: process.env.REDIS_PASSWORD
});
await cache.connect();
// Test cache operations
await cache.set('test-key', 'test-value', 300);
const value = await cache.get('test-key');
expect(value).toBe('test-value');
await cache.delete('test-key');
const deleted = await cache.get('test-key');
expect(deleted).toBeNull();
await cache.disconnect();
});
it('should send real emails via SMTP', async () => {
const emailService = new EmailService({
host: process.env.SMTP_HOST,
port: parseInt(process.env.SMTP_PORT),
auth: {
user: process.env.SMTP_USER,
pass: process.env.SMTP_PASS
}
});
const result = await emailService.send({
to: '[email protected]',
subject: 'Production Validation Test',
body: 'This is a real email sent during validation'
});
expect(result.messageId).toBeDefined();
expect(result.accepted).toContain('[email protected]');
});
});
5. Performance Under Load
// Validate performance with real load
describe('Performance Validation', () => {
it('should handle concurrent requests', async () => {
const apiClient = new APIClient(process.env.API_BASE_URL);
const concurrentRequests = 100;
const startTime = Date.now();
// Simulate real concurrent load
const promises = Array.from({ length: concurrentRequests }, () =>
apiClient.get('$health')
);
const results = await Promise.all(promises);
const endTime = Date.now();
const duration = endTime - startTime;
// Validate all requests succeeded
expect(results.every(r => r.status === 200)).toBe(true);
// Validate performance requirements
expect(duration).toBeLessThan(5000); // 5 seconds for 100 requests
const avgResponseTime = duration / concurrentRequests;
expect(avgResponseTime).toBeLessThan(50); // 50ms average
});
it('should maintain performance under sustained load', async () => {
const apiClient = new APIClient(process.env.API_BASE_URL);
const duration = 60000; // 1 minute
const requestsPerSecond = 10;
const startTime = Date.now();
let totalRequests = 0;
let successfulRequests = 0;
while (Date.now() - startTime < duration) {
const batchStart = Date.now();
const batch = Array.from({ length: requestsPerSecond }, () =>
apiClient.get('$api$users').catch(() => null)
);
const results = await Promise.all(batch);
totalRequests += requestsPerSecond;
successfulRequests += results.filter(r => r?.status === 200).length;
// Wait for next second
const elapsed = Date.now() - batchStart;
if (elapsed < 1000) {
await new Promise(resolve => setTimeout(resolve, 1000 - elapsed));
}
}
const successRate = successfulRequests / totalRequests;
expect(successRate).toBeGreaterThan(0.95); // 95% success rate
});
});
Validation Checklist
1. Code Quality Validation
# No mock implementations in production code
grep -r "mock\|fake\|stub" src/ --exclude-dir=__tests__ --exclude="*.test.*" --exclude="*.spec.*"
# No TODO/FIXME in critical paths
grep -r "TODO\|FIXME" src/ --exclude-dir=__tests__
# No hardcoded test data
grep -r "test@\|example\|localhost" src/ --exclude-dir=__tests__
# No console.log statements
grep -r "console\." src/ --exclude-dir=__tests__
2. Environment Validation
// Validate environment configuration
const validateEnvironment = () => {
const required = [
'DATABASE_URL',
'REDIS_URL',
'API_KEY',
'SMTP_HOST',
'JWT_SECRET'
];
const missing = required.filter(key => !process.env[key]);
if (missing.length > 0) {
throw new Error(`Missing required environment variables: ${missing.join(', ')}`);
}
};
3. Security Validation
// Validate security measures
describe('Security Validation', () => {
it('should enforce authentication', async () => {
const response = await request(app)
.get('$api$protected')
.expect(401);
expect(response.body.error).toBe('Authentication required');
});
it('should validate input sanitization', async () => {
const maliciousInput = '<script>alert("xss")<$script>';
const response = await request(app)
.post('$api$users')
.send({ name: maliciousInput })
.set('Authorization', `Bearer ${validToken}`)
.expect(400);
expect(response.body.error).toContain('Invalid input');
});
it('should use HTTPS in production', () => {
if (process.env.NODE_ENV === 'production') {
expect(process.env.FORCE_HTTPS).toBe('true');
}
});
});
4. Deployment R
Content truncated.
When not to use it
- →When running unit tests that require isolation from external systems
- →When the environment lacks access to production-like databases or APIs
Prerequisites
Limitations
- →Requires valid environment configurations to perform integration checks
- →May fail if external services are unreachable or misconfigured
How it compares
It shifts focus from isolated unit testing to verifying that the application functions correctly against real-world systems and infrastructure.
Compared to similar skills
agent-production-validator side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| agent-production-validator (this skill) | 3 | 6mo | Review | Advanced |
| validate-delivery | 1 | 5mo | Review | Beginner |
| release-testing | 1 | 1mo | Review | Advanced |
| documenso-ci-integration | 1 | 27d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ruvnet
View all by ruvnet →You might also like
validate-delivery
avifenesh
Use when validating task completion before shipping. Runs tests, build, and requirement checks. Returns pass/fail with fix instructions.
release-testing
mono
Run integration tests to verify SkiaSharp NuGet packages work correctly before publishing. Use when user asks to: - Test/verify packages before release - Run integration tests - Test on specific device (iPad, iPhone, Android emulator, Mac, Windows) - Verify SkiaSharp rendering works - Check if packages are ready for publishing - Run smoke/console/blazor/maui tests - Continue with release - Test version X Triggers: "test the release", "verify packages", "run tests on iPad", "check ios tests", "test mac catalyst", "run android tests", "continue", "test 3.119.2-preview.2".
documenso-ci-integration
jeremylongshore
Configure CI/CD pipelines for Documenso integrations. Use when setting up automated testing, deployment pipelines, or continuous integration for Documenso projects. Trigger with phrases like "documenso CI", "documenso GitHub Actions", "documenso pipeline", "documenso automated testing".
smoke-check
hoatv2211
Run core path smoke validation before QA handoff or merge.
aidlc-build
aws-samples
Final integration build and test verification. Validates that implemented code compiles, passes all test suites, and meets quality gates before deployment.
release-bump
himatts
Prepare versioned release updates for Lime Pipeline. Use when user-visible behavior changes require bumping `bl_info["version"]`, updating `CHANGELOG.md`, and producing release-ready QA notes.