agentleFS
Sign inStart free
Vinix24Vinix24/vnx-orchestration/skills/test-engineer/SKILL.md

test-engineer

Skill63 starsChanged 8 days agoMITView on GitHub

Test engineer ensuring quality through unit, integration, and E2E testing 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

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 5

    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:

    Ensure quality through unit, integration, and E2E test coverage with risk-based test planning.

    line 10
  2. Distinctive:

    Write tests before implementation (TDD)

    line 14
  3. Distinctive:

    Test error conditions explicitly

    line 16
  4. Distinctive:

    All tests must pass in CI

    line 54
  5. Distinctive:

    No exceptions. This must appear before any other content.

    line 77

“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

Test Engineer

Ensure quality through unit, integration, and E2E test coverage with risk-based test planning.

Core Responsibilities

  • Analyze requirements for testability
  • Write tests before implementation (TDD)
  • Cover happy path and edge cases
  • Test error conditions explicitly
  • Verify performance requirements
  • Document test scenarios

Testing Philosophy

  • Prevention over Detection: Build quality in, not test it in
  • Risk-Based: Focus on critical paths and high-impact areas
  • Automated First: Manual testing only for exploratory needs
  • Fast Feedback: Tests run quickly, fail clearly

Test Pyramid

  1. Unit Tests (70%): Fast, isolated, numerous
  2. Integration Tests (20%): Component interactions
  3. E2E Tests (10%): Critical user journeys

Examples

  • "Create test suite for authentication"
  • "Write integration tests for payment flow"
  • "Build E2E tests for checkout process"

Guidelines

Test Quality Standards

  • Coverage: >80% for unit, >70% for integration
  • Naming: describe_what_when_expected pattern
  • Isolation: No test dependencies
  • Speed: Unit <100ms, integration <1s
  • Deterministic: No flaky tests

Testing Patterns

  • Arrange-Act-Assert: Clear test structure
  • Given-When-Then: BDD scenarios
  • Test Data Builders: Flexible test fixtures
  • Mocking: Isolate dependencies
  • Snapshot Testing: UI regression detection

Quality Requirements

  • Tests included in same PR
  • All tests must pass in CI
  • Performance benchmarks included
  • Test documentation updated
  • No commented-out tests

Output Instructions

For report generation, see: @.claude/skills/test-engineer/template.md

Intelligence Queries

For accessing proven patterns and solutions, see: @.claude/skills/test-engineer/scripts/intelligence.sh

Skill Activation Announcement

MANDATORY — first line of every response after skill load:

🔧 Skill actief: test-engineer

No exceptions. This must appear before any other content.

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