Token导航 LogoToken导航

Agent Skill · 研究检索

testing-production(测试生产)

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

testing-production 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证为 MIT,第三方扫描有未通过项,按安装量在研究检索类的 73,675 个 Skill 里排第 52,984。

总安装 541周安装 23GitHub Stars 8下载 190核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:testing-production(测试生产)
来源仓库:https://github.com/vamseeachanta/workspace-hub
仓库路径:skills/testing-production
安装命令:
npx skills add https://github.com/vamseeachanta/workspace-hub --skill testing-production
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/vamseeachanta/workspace-hub --skill testing-production

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于辅助测试设计、自动化测试、用例整理和回归验证。适合编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需确认项目测试框架、运行命令和夹具数据,避免为通过测试而改坏真实逻辑。涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

安装方式:github,支持 Codex、Claude、Cursor、Gemini CLI。

来源仓库内路径:skills/testing-production

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/vamseeachanta/workspace-hub --skill testing-pr…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

testing-production 怎么安装?

在终端执行 npx skills add https://github.com/vamseeachanta/workspace-hub --skill testing-production。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

testing-production 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

testing-production 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

testing-production 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

testing-production 用的人多吗?

公开数据是累计安装 541 次,近一周安装 23 次,下载 190 次,GitHub 8 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

testing-production 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
testing-production

测试生产 · 本页

5418接触敏感数据MIT未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Production Validation

Ensuring applications are fully implemented, tested against real systems, and deployment-ready

Quick Start

# 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)

Core Concepts

Production Validation vs Unit Testing

AspectUnit Tests (TDD)Production Validation
DependenciesMockedReal
DatabaseIn-memory/fakeActual PostgreSQL/etc
APIsStubbed responsesLive service calls
PurposeDesign/logicDeployment readiness
SpeedFast (ms)Slower (seconds)

Validation Categories

  1. Implementation Completeness: No mock/stub/fake code in production
  2. Database Integration: CRUD operations on real database
  3. External APIs: Actual service integrations work
  4. Infrastructure: Cache, email, queues function correctly
  5. Performance: Meets latency and throughput requirements
  6. Security: Authentication, authorization, input validation

Implementation Pattern

1. Implementation Completeness Check

const validateImplementation = async (codebase: string[]): Promise<Violation[]> => {
  const violations: Violation[] = [];

  // Patterns indicating incomplete implementation
  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 Validation

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,
      port: parseInt(process.env.TEST_DB_PORT || '5432'),
      ssl: true
    });
  });

  afterAll(async () => {
    await realDatabase.disconnect();
  });

  it('should perform complete CRUD operations', async () => {
    const repository = new UserRepository(realDatabase);

    // CREATE
    const user = await repository.create({
      email: 'validation-test@example.com',
      name: 'Validation Test'
    });
    expect(user.id).toBeDefined();
    expect(user.createdAt).toBeInstanceOf(Date);

    // READ
    const retrieved = await repository.findById(user.id);
    expect(retrieved).toEqual(user);

    // UPDATE
    const updated = await repository.update(user.id, { name: 'Updated Name' });
    expect(updated.name).toBe('Updated Name');

    // DELETE
    await repository.delete(user.id);
    const deleted = await repository.findById(user.id);
    expect(deleted).toBeNull();
  });
});

3. External API Validation

describe('External API Validation', () => {
  it('should integrate with real payment service', async () => {
    const paymentService = new PaymentService({
      apiKey: process.env.STRIPE_TEST_KEY,
      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');
  });
});

Configuration

production_validation:
  scan:
    patterns:
      - "mock"
      - "fake"
      - "stub"
      - "TODO"
      - "FIXME"
      - "not implemented"
    exclude_dirs:
      - "__tests__"
      - "tests"
      - "spec"
      - "node_modules"
    exclude_files:
      - "*.test.*"
      - "*.spec.*"

  database:
    use_real: true
    host: ${TEST_DB_HOST}
    cleanup_after: true

  external_apis:
    use_test_mode: true
    timeout_ms: 30000
    retry_count: 3

  performance:
    concurrent_requests: 100
    max_latency_ms: 200
    min_throughput_rps: 1000
    sustained_duration_s: 60

Usage Examples

Example 1: Complete Validation Suite

describe('Production Readiness Validation', () => {
  describe('Implementation Completeness', () => {
    it('should have no mock implementations in production code', async () => {
      const result = await exec(
        'grep -r "mock\\|fake\\|stub" src/ --exclude-dir=__tests__ --exclude="*.test.*"'
      );
      expect(result.stdout).toBe('');
    });

    it('should have no TODO/FIXME in critical paths', async () => {
      const result = await exec('grep -r "TODO\\|FIXME" src/');
      expect(result.stdout).toBe('');
    });

    it('should have no hardcoded test data', async () => {
      const result = await exec(
        'grep -r "test@\\|example\\|localhost" src/ --exclude-dir=__tests__'
      );
      expect(result.stdout).toBe('');
    });
  });

  describe('Environment Configuration', () => {
    it('should have all required environment variables', () => {
      const required = [
        'DATABASE_URL',
        'REDIS_URL',
        'API_KEY',
        'SMTP_HOST',
        'JWT_SECRET'
      ];

      const missing = required.filter(key => !process.env[key]);
      expect(missing).toEqual([]);
    });
  });
});

Example 2: Infrastructure Validation

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 || '6379'),
      password: process.env.REDIS_PASSWORD
    });

    await cache.connect();

    // Test cache operations
    await cache.set('validation-key', 'test-value', 300);
    const value = await cache.get('validation-key');
    expect(value).toBe('test-value');

    await cache.delete('validation-key');
    const deleted = await cache.get('validation-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 || '587'),
      auth: {
        user: process.env.SMTP_USER,
        pass: process.env.SMTP_PASS
      }
    });

    const result = await emailService.send({
      to: 'validation-test@example.com',
      subject: 'Production Validation Test',
      body: 'This is a real email sent during validation'
    });

    expect(result.messageId).toBeDefined();
    expect(result.accepted).toContain('validation-test@example.com');
  });
});

Example 3: Performance Validation

describe('Performance Validation', () => {
  it('should handle concurrent requests within latency requirements', async () => {
    const apiClient = new APIClient(process.env.API_BASE_URL);
    const concurrentRequests = 100;
    const startTime = Date.now();

    const promises = Array.from({ length: concurrentRequests }, () =>
      apiClient.get('/health')
    );

    const results = await Promise.all(promises);
    const duration = Date.now() - startTime;

    // All requests succeeded
    expect(results.every(r => r.status === 200)).toBe(true);

    // Within 5 seconds for 100 requests
    expect(duration).toBeLessThan(5000);

    // Average response time under 50ms
    const avgResponseTime = duration / concurrentRequests;
    expect(avgResponseTime).toBeLessThan(50);
  });

  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;

      // Throttle to maintain rate
      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
  });
});

Example 4: Security Validation

describe('Security Validation', () => {
  it('should enforce authentication on protected routes', async () => {
    const response = await request(app)
      .get('/api/protected')
      .expect(401);

    expect(response.body.error).toBe('Authentication required');
  });

  it('should validate and sanitize input', 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');
    }
  });

  it('should have proper health check endpoint', async () => {
    const response = await request(app)
      .get('/health')
      .expect(200);

    expect(response.body).toMatchObject({
      status: 'healthy',
      timestamp: expect.any(String),
      uptime: expect.any(Number),
      dependencies: {
        database: 'connected',
        cache: 'connected',
        external_api: 'reachable'
      }
    });
  });
});

Execution Checklist

  • Scan for mock/fake/stub implementations
  • Scan for TODO/FIXME comments
  • Verify all environment variables configured
  • Test database CRUD with real database
  • Test external APIs with real (test mode) services
  • Test infrastructure (cache, email, queues)
  • Validate performance under load
  • Verify security measures (auth, input validation)
  • Test health check endpoint
  • Verify graceful shutdown handling

Best Practices

Real Data Usage

  • Use production-like test data, not placeholder values
  • Test with actual file uploads, not mock files
  • Validate with real user scenarios and edge cases

Infrastructure Testing

  • Test against actual databases, not in-memory alternatives
  • Validate network connectivity and timeouts
  • Test failure scenarios with real service outages

Performance Validation

  • Measure actual response times under load
  • Test memory usage with real data volumes
  • Validate scaling behavior with production-sized datasets

Security Testing

  • Test authentication with real identity providers
  • Validate encryption with actual certificates
  • Test authorization with real user roles and permissions

Error Handling

Mock Found in Production Code

# Identify and report violations
grep -rn "mock\|fake\|stub" src/ --exclude-dir=__tests__ | while read line; do
  echo "VIOLATION: $line"
  echo "ACTION: Replace with real implementation"
done

External Service Unavailable

// Graceful handling of service outages during validation
try {
  await validateExternalService(service);
} catch (error) {
  if (error.code === 'ECONNREFUSED') {
    console.warn(`Service ${service.name} unavailable - skipping validation`);
    skippedValidations.push(service.name);
  } else {
    throw error;
  }
}

// Report skipped validations
if (skippedValidations.length > 0) {
  console.warn(`Skipped validations: ${skippedValidations.join(', ')}`);
  console.warn('These MUST be validated before production deploy');
}

Metrics & Success Criteria

ValidationPass Criteria
Mock-Free Code0 mock/fake/stub in production code
Database IntegrationAll CRUD operations work
API IntegrationAll external APIs respond correctly
Performancep99 < 200ms, > 1000 req/s
SecurityAll auth/authz tests pass
Health CheckReturns healthy status
Error Rate< 0.1% under load

Integration Points

MCP Tools

// Store validation results
  action: "store",
  namespace: "production-validation",
  key: "validation_report_" + Date.now(),
  value: JSON.stringify({
    timestamp: new Date().toISOString(),
    violations: violations,
    passed: validations.passed,
    failed: validations.failed
  })
});

Hooks

# Pre-deploy: Run production validation

# Post-validation: Report results

Related Skills

References

Version History

  • 1.0.0 (2026-01-02): Initial release - converted from production-validator agent

平台分布

Claude Code

31.74%
按下载量换算60

Antigravity

22.14%
按下载量换算42

windsurf

17.02%
按下载量换算32

trae

12.63%
按下载量换算24

OpenCode

7.41%
按下载量换算14

Cursor

3.3%
按下载量换算6

安全审计

Gen Agent Trust Hub

未通过

Socket

可疑

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills