dev-testing
/dev-testing
This skill should be used when developing or maintaining s2s plugin code. Provides check definitions for instruction quality, consistency, resume capability, and edge cases. NOT SHIPPED with plugin.
- Author
- spec2ship ↗
- Repository
- spec2ship ↗
- Licence
- MIT
- Last repository change
- 12.07.2026
Assessment and security
- Files in this package
- 9
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
This skill should be used when developing or maintaining s2s plugin code. Provides check definitions for instruction quality, consistency, resume capability, and edge cases. NOT SHIPPED with plugin.
Original author description
This skill should be used when developing or maintaining s2s plugin code. Provides check definitions for instruction quality, consistency, resume capability, and edge cases. NOT SHIPPED with plugin.
How it works
- Purpose
- When to Use
- Check Categories
- References
- Integration
- Adding New Checks
SKILL.md preview
---
name: dev-testing
description: "This skill should be used when developing or maintaining s2s plugin code. Provides check definitions for instruction quality, consistency, resume capability, and edge cases. NOT SHIPPED with plugin."
version: 0.1.0
---
# Development Testing Skill
> **NOT SHIPPED**: This skill is for s2s contributors only.
This skill provides check and test definitions for validating s2s plugin code quality. It is used by the `dev-validator` agent.
## Purpose
Centralized definitions for all development checks and tests:
- **INST-***: Instruction quality (commands/agents follow patterns)
- **CONS-***: Consistency across commands
- **RES-***: Resume capability verification
- **EDGE-***: Edge case scenarios
## When to Use
This skill is automatically loaded when:
- Running `/s2s:dev:check`
- Running `/s2s:dev:test`
- Asking about "development checks", "plugin validation", "test s2s code"
## Check Categories
| Category | Purpose | Count | Severity Range |
|----------|---------|-------|----------------|
| INST-* | Instruction quality | 11 | medium-critical |
| CONS-* | Cross-command consistency | 7 | medium-high |
| RES-* | Resume capability | 7 | high-critical |
| EDGE-* | Edge case handling | 7 | medium-high |
Total: **32 checks**
## References
| File | Content |
|------|---------|
| `check-registry.md` | Master list of all checks with metadata |
| `inst-checks.md` | INST-* check definitions |
| `cons-checks.md` | CONS-* check definitions |
| `res-checks.md` | RES-* check definitions |
| `edge-scenarios.md` | EDGE-* scenario definitions |
| `roundtable-tests.md` | Test baseline for TECH-002 refactoring |
| `extension-guide.md` | How to add new checks (templates included) |
## Integration
```
/s2s:dev:check
└── dev-validator agent
└── reads from this skill's references/
/s2s:dev:test
└── dev-validator agent
└── reads from this skill's references/
```
## Adding New Checks
**Read `extension-guide.md`** for complete instructions with templates.
Quick overview:
1. Choose category (INST/CONS/RES/EDGE)
2. Add entry to `check-registry.md`
3. Add full definition using template from `extension-guide.md`
4. Update count in this file
5. Test with `/s2s:dev:check --all` or `/s2s:dev:test --all`
Files in this package (9)
- SKILL.md 2 KB
- references/check-registry.md 8 KB
- references/cons-checks.md 11 KB
- references/edge-scenarios.md 8 KB
- references/extension-guide.md 7 KB
- references/inst-checks.md 19 KB
- references/res-checks.md 10 KB
- references/roundtable-tests.md 22 KB
- references/strategy-hook-anchor-check.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · spec2ship/spec2ship | 100 | MIT |
| codeaholicguy/ai-devkit | 90 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version f6352024a959 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100evaluate-plugin
Evaluate plugin quality. Use when user says \"evaluate plugin\", \"review plugin quality\", \"score my plugin\", \"check plugin\", \"rate plugin\". - 100meta-plugin-structure
Use when the user asks to ”create a plugin”, ”scaffold a plugin”, or ”understand plugin structure” for Claude Code. - 90test-gen
Use when generating tests for untested code — happy path, edge cases, error handling - 100medusa-plugins
Develop and publish Medusa v2 plugins — plugin structure, plugin vs module comparison, npm packaging, and reusable plugin template. Use when building distributable Medusa extensions. - 100test-scenarios
Derives QA test scenarios and acceptance test cases from a spec or user story, covering happy paths, edge cases, error states, data variations, and ML quality-bar/eval cases. Use when you need to "write test cases for this story," "figure out what QA should check," "turn this… - 100qa-engineer
Use when writing test plans, designing test cases, identifying edge cases and failure scenarios, reviewing code for testability, setting up test automation, evaluating test coverage, performing exploratory testing, defining quality standards, or any task focused on ensuring…