agentleFS
Sign inStart free
Data-WiseData-Wise/craft/skills/testing/test-strategist/SKILL.md

test-strategist

Skill4 starsChanged 12 days agoMITView on GitHub

This skill should be used when the user asks to "plan test strategy", "improve test coverage", "fix flaky tests", "optimize test performance", or needs guidance on testing infrastructure and quality assurance. Provides expert guidance on test strategy design, coverage analysis, and test quality improvement.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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 this skill when:

    line 12
  2. Distinctive:

    Test plans with prioritized cases

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Strategist Skill

Expert in test strategy, coverage optimization, and quality assurance.

When to Use

Use this skill when:

  • Planning test strategy for new features
  • Improving test coverage
  • Debugging flaky or failing tests
  • Optimizing test performance
  • Setting up testing infrastructure

Capabilities

Test Strategy Design

  • Unit, integration, and e2e test planning
  • Test pyramid optimization
  • Coverage target recommendations
  • Test isolation strategies

Coverage Analysis

  • Identify untested code paths
  • Suggest high-value test cases
  • Coverage metric interpretation
  • Risk-based testing priorities

Test Quality

  • Flaky test detection and fixes
  • Test performance optimization
  • Mock and fixture best practices
  • Test maintainability improvements

Framework Expertise

  • pytest, unittest (Python)
  • Jest, Vitest, Mocha (JavaScript)
  • testthat (R)
  • go test (Go)
  • cargo test (Rust)

Example Prompts

"Help me create a test strategy for our authentication module"
"Why is this test flaky and how do I fix it?"
"What tests should I add to improve coverage of the payment flow?"
"How do I structure integration tests for our API?"
"Suggest mocking strategies for external service dependencies"

Outputs

  • Test plans with prioritized cases
  • Coverage improvement recommendations
  • Flaky test analysis and fixes
  • Test refactoring suggestions
  • Performance optimization tips

Integration

Works with:

  • /craft:test - Execute tests
  • /craft:test --coverage - Coverage reports
  • /craft:test debug - Debug failures
  • /craft:ci:local - CI validation

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