Test Strategy Gap Review
Use when the main question is whether current verification is sufficient for a change, which test layers are missing, and where the smallest high-value regression protection should be added.
Install
$ agentstack add skill-motao123-dev-workflow-kit-test-strategy-gap-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-motao123-dev-workflow-kit-test-strategy-gap-review) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Test Strategy Gap Review
Use this skill when the issue is not a failing test, but uncertainty about whether the current test strategy is strong enough.
Trigger Conditions
Use this skill when:
- the user asks what tests are missing
- a risky change has weak or uneven verification coverage
- the team is unsure whether to add unit, integration, contract, browser, or smoke coverage
- the change is hard to ship confidently because test coverage feels incomplete
- there is concern that current tests exist but do not protect the right behaviors
Do not use this skill for root-cause debugging of a failing test or for CI triage when the failure is already known.
Workflow
- Identify the change and its highest-risk behaviors.
- Review existing verification surfaces.
- Identify missing or weak coverage layers.
- Separate must-add coverage from nice-to-have coverage.
- Recommend the smallest high-value additions.
- Suggest the next verification or implementation step.
Output
For non-trivial work, provide:
- current verification picture
- missing or weak test layers
- highest-risk blind spots
- smallest useful coverage additions
- recommended next step
Coordination
After test strategy review:
- use
change-impact-analysisif the affected surface is still unclear - move into the active implementation workflow to add or adjust verification
- use
ship-readinesswhen test coverage is the last release blocker
Invocation Examples
- "Use test-strategy-gap-review to tell me what coverage is missing before we merge this change."
- "Use test-strategy-gap-review to decide whether this needs unit, integration, or browser checks."
- "Use test-strategy-gap-review because the current tests exist, but I don't trust that they cover the risky behavior."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: motao123
- Source: motao123/dev-workflow-kit
- License: MIT
- Homepage: https://motao123.github.io/dev-workflow-kit/
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.