testing-unit
Testing Unit
Overview
Use this skill to validate small-scope logic quickly and deterministically with strong failure localization.
Scope Boundaries
- Use when correctness can be validated within isolated units.
- Typical requests:
Harden branch and edge-case logic with fast deterministic tests.Verify exception paths and guard-rail behavior.Isolate dependencies to pinpoint failure causes.
- Do not use when:
- Cross-service compatibility is the core risk (
testing-contract/testing-integration). - Full UI journey behavior is needed (
testing-e2e/playwright).
- Cross-service compatibility is the core risk (
Inputs
- Unit boundaries and behavior expectations
- Mock/stub strategy and dependency seams
- Runtime constraints for fast feedback loops
Outputs
- Unit suite with fixture and isolation strategy
- Decision record for scope and assertion depth
- Verification checklist for edge/failure coverage
Workflow
- Identify unit boundaries and observable contracts.
- Define edge and failure conditions before implementation.
- Compare isolation strategies and choose one with rationale.
- Implement deterministic tests with explicit assertions.
- Publish residual risks and uncovered dependency behaviors.
Quality Gates
- Unit scope is explicit and dependency control is intentional.
- Edge and failure cases are covered for critical logic.
- Tests are deterministic and fast enough for frequent execution.
- Evidence is reproducible and actionable.
Failure Handling
- Stop when critical units lack edge/failure coverage.
- Escalate when isolation requires architectural refactoring.
Bundled Resources
references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9