Tdd Guide

v2.1.1

Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows a...

4· 3.5k·19 current·19 all-time
byAlireza Rezvani@alirezarezvani
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (TDD, test generation, coverage analysis, framework conversion) align with the provided scripts (test_generator.py, coverage_analyzer.py, fixture_generator.py, framework_adapter.py, etc.) and documentation. Required env vars/binaries/config paths are none, which is proportionate for a local analysis/generation tool.
Instruction Scope
SKILL.md instructs the agent to accept source code and coverage reports, run the included Python scripts, and produce test stubs/reports. The instructions reference only local files and coverage formats relevant to the stated purpose; they do not instruct reading unrelated system state, secrets, or exfiltrating data.
Install Mechanism
No install spec is declared (instruction-only skill). The package includes Python scripts and docs but does not download remote binaries or extract archives during install. This is low-risk relative to the skill's function.
Credentials
The skill declares no required environment variables, credentials, or config paths. The README shows an example of uploading a skill via an API (demonstrative) but the skill itself does not demand an API key or unrelated secrets.
Persistence & Privilege
Skill flags are default (always: false, agent invocation allowed). It does not request permanent/system-wide presence or claim to modify other skills or system settings.
Assessment
This skill appears coherent and matches its stated purpose, but before running any included scripts: (1) review the remaining (truncated) files for any network calls or subprocess execution, (2) inspect test_generator.py to ensure it generates code safely (don't auto-run generated tests against production systems), and (3) execute the scripts in an isolated environment (container or sandbox) when first using with sensitive code. Also manually review generated tests and fixtures before committing them to your codebase.

Like a lobster shell, security has layers — review code before you run it.

latestvk978thevc5cs7tyz43cevm4a0982jsp3

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments