AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Test Strategy

skill-jakesterns-agent-skills-test-strategy · by jakesterns

Designs a focused test plan for a feature, bug fix, refactor, or release by choosing the right unit, integration, end-to-end, and regression tests.

↗ Repository
— No reviews yet
0 installs
18 views
0.0% view→install

Install

$ agentstack add skill-jakesterns-agent-skills-test-strategy

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Test Strategy? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Test Strategy

Use this skill when a user asks what to test, how much to test, or how to validate a change before release.

Inputs

  • Feature, bug fix, refactor, pull request, or release scope
  • Existing test framework and commands
  • Known risks, production incidents, or edge cases

Steps

  1. Identify behaviors that must remain true, not just lines of code that changed.
  2. Map risks to test levels: unit for pure logic, integration for contracts and data flow, end-to-end for critical user journeys, regression tests for bugs.
  3. Prioritize tests by impact, likelihood, and cost to maintain.
  4. Include negative cases, boundary cases, permissions, failure modes, and compatibility cases.
  5. Recommend test data and mocks only where they preserve realism.
  6. Define the smallest useful test suite for this change and the broader suite for release confidence.
  7. Provide commands to run if they can be inferred from the repo.

Output

Return:

  • Risk-based test matrix
  • Recommended new or updated tests
  • Existing tests to run
  • Gaps that require manual QA or instrumentation
  • Confidence assessment

Guidelines

  • Avoid blanket "add more tests" advice.
  • Prefer tests that fail for the right reason.
  • Keep tests aligned with user-visible behavior and stable contracts.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills