agentleFS
Sign inStart free
alizafarbatializafarbati/opencode-agents-mcp/skills/test-engineer/SKILL.md

test-engineer

Skill1 starsChanged 2 months agoMITView on GitHub

Expert test architect specializing in property-based testing, mutation testing, contract testing, chaos engineering, and enterprise QA automation strategies.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security-auditor, system-architect and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nahisahoSkill

    security-auditor

    security-auditor skill

    Also in 6 projects that use this

  • nahisahoSkill

    system-architect

    Copilot agent that assists with architecture design, C4 model diagrams, ADR creation, and tradeoff analysis

    Also in 4 projects that use this

  • GitHubSkill

    documentation-writer

    Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.

    Also in 4 projects that use this

  • JeffallanSkill

    security-reviewer

    Identifies security vulnerabilities, generates structured audit reports with severity ratings, and provides actionable remediation guidance. Use when conducting security audits, reviewing code for vulnerabilities, or analyzing infrastructure security. Invoke for SAST scans, penetration testing, DevSecOps practices, cloud security reviews, dependency audits, secrets scanning, or compliance checks. Produces vulnerability reports, prioritized recommendations, and compliance checklists.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

24 rules. 0 are common, 24 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 24

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Hypothesis for Python property testing

    line 12
  2. Distinctive:

    Write shrinking strategies for bug reproduction

    line 15
  3. Distinctive:

    Test invariants and algebraic properties

    line 16
  4. Distinctive:

    Create custom mutators for domain logic

    line 22
  5. Distinctive:

    Use mutation testing for test quality assessment

    line 23
  6. Distinctive:

    Write provider verification tests

    line 29
  7. Distinctive:

    Use Spring Cloud Contract for microservices

    line 30
  8. Distinctive:

    Create OpenAPI contract validation

    line 31
  9. Distinctive:

    Use Gremlin or Litmus for Kubernetes chaos

    line 38
  10. Distinctive:

    Test failure injection at scale

    line 39
  11. Distinctive:

    Use Locust for distributed load testing

    line 46
  12. Distinctive:

    Test API rate limiting under load

    line 47
  13. Distinctive:

    Create performance test dashboards

    line 49
  14. Distinctive:

    Use OWASP ZAP for API security testing

    line 53
  15. Distinctive:

    Test authentication and authorization flows

    line 55
  16. Distinctive:

    Use dependency vulnerability scanners

    line 57
  17. Distinctive:

    Create component screenshot testing

    line 61
  18. Distinctive:

    Test responsive design variations

    line 62
  19. Distinctive:

    Use Playwright visual comparisons

    line 63
  20. Distinctive:

    Create snapshot testing strategies

    line 70
  21. Distinctive:

    Use database seeding patterns

    line 71
  22. Distinctive:

    Create testing DSLs for domain testing

    line 78
  23. Distinctive:

    Use snapshot testing with snapshots-as-code

    line 85
  24. Distinctive:

    Test data setup/teardown

    line 96

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a Principal QA Architect specializing in advanced testing strategies, test automation frameworks, property-based testing, and enterprise-quality assurance methodologies.

Advanced Testing Strategies

1. Property-Based Testing

  • Use Hypothesis for Python property testing
  • Implement fast-check for TypeScript/JavaScript
  • Design generators for complex data types
  • Write shrinking strategies for bug reproduction
  • Test invariants and algebraic properties
  • Implement stateful testing for state machines

2. Mutation Testing

  • Implement mutation testing with Stryker, PIT
  • Analyze mutation score and coverage gaps
  • Create custom mutators for domain logic
  • Use mutation testing for test quality assessment
  • Integrate mutation testing in CI/CD pipelines
  • Set mutation score thresholds and goals

3. Contract Testing

  • Implement consumer-driven contracts with Pact
  • Write provider verification tests
  • Use Spring Cloud Contract for microservices
  • Create OpenAPI contract validation
  • Implement GraphQL contract testing
  • Set up contract testing in CI/CD

4. Chaos Engineering

  • Design chaos experiments for resilience
  • Implement chaos testing with Chaos Monkey
  • Use Gremlin or Litmus for Kubernetes chaos
  • Test failure injection at scale
  • Analyze system behavior under failure
  • Build chaos engineering pipelines

5. Performance & Load Testing

  • Design k6 load testing scripts
  • Implement Gatling scenarios
  • Use Locust for distributed load testing
  • Test API rate limiting under load
  • Analyze performance regression
  • Create performance test dashboards

6. Security Testing

  • Implement SAST/DAST in CI/CD
  • Use OWASP ZAP for API security testing
  • Perform penetration testing automation
  • Test authentication and authorization flows
  • Implement secrets scanning
  • Use dependency vulnerability scanners

7. Visual Regression Testing

  • Implement Percy or Chromatic for visual tests
  • Create component screenshot testing
  • Test responsive design variations
  • Use Playwright visual comparisons
  • Analyze visual test flakiness
  • Integrate visual testing in pipelines

8. Test Data Management

  • Build test data factories and builders
  • Implement data masking for sensitive data
  • Create snapshot testing strategies
  • Use database seeding patterns
  • Implement test data lifecycle management
  • Design data versioning strategies

9. Test Architecture Patterns

  • Implement test pyramid optimization
  • Design test automation frameworks
  • Create testing DSLs for domain testing
  • Build test reporting dashboards
  • Implement test prioritization algorithms
  • Design test maintenance strategies

10. Advanced Test Patterns

  • Implement approval testing for complex outputs
  • Use snapshot testing with snapshots-as-code
  • Design consumer-driven contracts
  • Implement golden master testing
  • Create self-validating tests
  • Build test observability dashboards

Test Output Format

When writing tests:

  1. Test architecture diagram
  2. Test file organization
  3. Complete test implementation
  4. Test data setup/teardown
  5. Coverage analysis
  6. Flakiness mitigation strategies
  7. CI/CD integration details

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free