
Agent Production Validator
Run a production-readiness pass that rejects mock implementations and drives real E2E and production test suites before deploy.
Overview
Agent Production Validator is an agent skill most often used in Ship (also Operate) that ensures applications are fully implemented, free of mock backends, and exercised with production-oriented and E2E tests.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-production-validatorWhat is this skill?
- Pre-hook scans src/ for mock, fake, stub, TODO, and FIXME before validation starts
- Verifies fully implemented components with no placeholder backends
- Post-hook runs npm run test:production and test:e2e when package.json defines them
- Validates real databases, APIs, and services—not stubbed integrations
- Marked critical-priority validator type in skill metadata
Adoption & trust: 639 installs on skills.sh; 58.5k GitHub stars; 0/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your app passes local tests but may still ship with mocks, stubs, or untested real integrations.
Who is it for?
Indie builders about to tag a release who want an agent-enforced gate against fake data layers and missing real-service tests.
Skip if: Early prototypes intentionally using mocks, or repos without npm scripts or real integration endpoints to test against.
When should I use this skill?
Invoke $agent-production-validator when you need production validation, implementation verification against real systems, or deployment readiness checks.
What do I get? / Deliverables
You confirm no mock implementations remain in src/, run production and E2E suites when configured, and leave the codebase closer to deployment-ready.
- Mock/fake/stub scan results for src/
- Production and E2E test execution log when scripts exist
- Deployment readiness validation summary
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship because the skill’s job is verification and deployment readiness immediately before release. Testing subphase matches implementation verification, E2E execution, and scanning for mock/fake/stub code called out in hooks.
Where it fits
Invoke before merging a release branch so grep catches remaining mock|fake|stub in src/.
Final gate before tagging v1.0 when package.json exposes test:production and test:e2e.
Re-run after hotfixes to ensure new shortcuts did not reintroduce TODO/FIXME placeholders.
How it compares
Use as a deployment-readiness validator with shell hooks, not as a substitute for structured code review or security scanning skills.
Common Questions / FAQ
Who is agent-production-validator for?
Solo builders and small teams shipping Node or npm-based apps who need an agent to verify real implementations before production deploy.
When should I use agent-production-validator?
In Ship before release to scan for mocks and run test:production/test:e2e; in Operate when re-validating after large refactors that might reintroduce stubs.
Is agent-production-validator safe to install?
It runs grep and npm test commands against your repo—review the Security Audits panel on this page and confirm hooks match your CI policies before use.
SKILL.md
READMESKILL.md - Agent Production Validator
--- 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 1. **Implementation Verification**: Ensure all components are fully implemented, not mocked 2. **Production Readiness**: Validate applications work with real databases, APIs, and services 3. **End-to-End Testing**: Execute comprehensive tests against actual system integrations 4. **Deployment Validation**: Verify applications function correctly in production-like environments 5. **Performance Validation**: Confirm real-world performance meets requirements ## Validation Strategies ### 1. Implementation Completeness Check ```typescript // 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 ```typescript // 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: 'test@example.com', 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 ```typescrip