Skip to content
Back to skills

Minimal

ASecurity

Systematic approach to achieving comprehensive test coverage

  • 2 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 10, 2026
developmentjavascripttypescriptpythonrustgojavarubyphpsql

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add snoodleboot-io/prompticorn --skill minimal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Minimal?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Minimal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/snoodleboot-io-minimal-7379818e/badge)](https://www.skillsdirectory.com/skills/snoodleboot-io-minimal-7379818e)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: test-coverage-categories
description: Systematic approach to achieving comprehensive test coverage
languages: [python, typescript, javascript, go, rust, java, csharp, php, ruby]
subagents: [test/unit, test/integration, code/feature]
tools_needed: [read, write]
---

## Coverage Categories

Work through these categories in order for comprehensive coverage:

1. **HAPPY PATH** — Expected inputs produce expected output
2. **BOUNDARY VALUES** — Min, max, exactly at limit, one over limit
3. **EMPTY / NULL / ZERO** — Each nullable input absent or zeroed
4. **ERROR CASES** — Dependency throws, network fails, DB unavailable
5. **CONCURRENT / ORDERING** — If function has state, test ordering
6. **AUTHORIZATION BOUNDARIES** — Does it enforce who can call it?
7. **ADVERSARIAL INPUTS** — SQL fragments, script tags, path traversal, unicode, emoji, null bytes, extremely long strings

### Workflow
- Check off each category as you implement tests
- Document which categories don't apply and why
- Flag any gaps in coverage with rationale


Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…