a5c-ai/test-driven-development
library/methodologies/rpikit/skills/test-driven-development/SKILL.md
Test-first development practice where test specifications are written before production code, integrated into plan tasks as mandatory first sub-steps.
$ install --global
skillsauthnpx skillsauth add a5c-ai/babysitter test-driven-developmentInstall 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 1, 2026, 12:14 PM55.5s2 files scanned
SKILL.md
- name:
- test-driven-development
- description:
- Test-first development practice where test specifications are written before production code, integrated into plan tasks as mandatory first sub-steps.
- allowed-tools:
- Read, Write, Edit, Bash, Grep, Glob, Agent, AskUserQuestion
Test-Driven Development
Overview
Every code-changing task must enumerate tests before implementation. Test specification is always the first sub-step of each task in the plan.
When to Use
- During plan writing (test strategy per task)
- During implementation (write tests before code)
- When verifying step completion
Process
- Specify tests first - Define inputs, expected outputs, edge cases
- Write test code - Create automated tests matching specification
- Implement production code - Write code that passes the tests
- Verify - Run tests and confirm all pass
Test Categories
- Unit tests: Isolated function/method testing
- Integration tests: Cross-component interaction testing
- Manual verification: Human-performed checks when automation is impractical
Key Rules
- Never combine test writing and implementation into a single step
- Every task with code changes must have associated tests
- Tests must be runnable and produce clear pass/fail results
- Edge cases must be explicitly considered
Tool Use
Integrated into methodologies/rpikit/rpikit-plan and methodologies/rpikit/rpikit-implement
Related Skills
a5c-ai/model-card-generator
development
VerifiedTrustedCommunity
Model documentation skill for generating model cards following Google's model card framework.
680SKILL.mdUpdated Apr 28, 2026
a5c-ai/mlflow-experiment-tracker
development
VerifiedTrustedCommunity
MLflow integration skill for experiment tracking, model registry, and artifact management. Enables LLMs to log experiments, compare runs, manage model lifecycle, and retrieve artifacts through the MLflow API.
680SKILL.mdUpdated Apr 28, 2026
a5c-ai/lime-explainer
data-ai
VerifiedTrustedCommunity
LIME-based local explanation skill for individual predictions across tabular, text, and image data.
680SKILL.mdUpdated Apr 28, 2026
a5c-ai/kubeflow-pipeline-executor
devops
VerifiedTrustedCommunity
Kubeflow Pipelines skill for ML workflow orchestration, component management, and Kubernetes-native ML.
680SKILL.mdUpdated Apr 28, 2026