packbot/write-tests
.claude/skills/write-tests/SKILL.md
Write comprehensive tests following the Analyze > Strategy > Implement > Verify workflow. Use when adding tests, improving coverage, or when the user asks to write tests for specific code.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add packbot/agentic-coding-boilerplate write-testsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 9:05 PM4.3s1 file scanned
SKILL.md
- name:
- write-tests
- description:
- Write comprehensive tests following the Analyze > Strategy > Implement > Verify workflow. Use when adding tests, improving coverage, or when the user asks to write tests for specific code.
- disable-model-invocation:
- true
Write Tests: $ARGUMENTS
Phase 1: Analyze
- Read the code to test: $ARGUMENTS
- Identify all public functions, methods, and APIs
- Map out the behavior: inputs > processing > outputs/side effects
- List edge cases: null/undefined, empty collections, boundary values, error conditions
- Check existing tests — extend coverage, don't duplicate
Phase 2: Strategy
Determine the right test types:
- Unit tests: For pure functions, business logic, utilities
- Integration tests: For code that interacts with databases, APIs, file system
- E2E tests: For critical user workflows (use sparingly)
Test naming convention:
describe("ModuleName", () => {
describe("functionName", () => {
it("should [expected behavior] when [condition]", () => {
Phase 3: Implement
Write tests following this priority:
- Happy path — The main use case works correctly
- Edge cases — Boundary values, empty inputs, null handling
- Error cases — Invalid inputs, network failures, permission errors
- Integration points — Interactions with external systems (mocked at boundaries)
Guidelines:
- Each test tests ONE behavior
- Tests are independent — no shared mutable state, no execution order dependencies
- Use descriptive assertion messages
- Mock at system boundaries (DB, API, file system), not internal functions
- Arrange > Act > Assert pattern in every test
Phase 4: Verify
- [ ] All new tests pass:
{{TEST_COMMAND}} - [ ] All existing tests still pass
- [ ] Tests fail for the right reason when the implementation is broken
- [ ] No test depends on another test's execution
- [ ] No hardcoded test data that could become stale
- [ ] Tests cover happy path, edge cases, and error cases
Related Skills
packbot/.claude/skills/review-code
development
VerifiedTrustedCommunity
Review code changes or a GitHub PR
SKILL.mdUpdated Apr 16, 2026
packbot/refactor
development
VerifiedTrustedCommunity
Refactor code safely following the Analyze > Plan > Refactor > Verify workflow. The key rule is that behavior must not change. Use when improving code structure, readability, or modularity.
SKILL.mdUpdated Apr 16, 2026
packbot/push
tools
VerifiedTrustedCommunity
Push commits to remote and optionally create a PR. Use when the user wants to push their changes.
SKILL.mdUpdated Apr 16, 2026
packbot/implement-feature
development
VerifiedTrustedCommunity
Implement a new feature following the Explore > Plan > Implement > Verify workflow. Use when adding new functionality, building a feature, or when the user asks to implement something.
SKILL.mdUpdated Apr 16, 2026