TDD Workflow

Test-driven development workflow enforcing 80%+ code coverage with unit, integration, and E2E tests. Write tests first, validate RED state, implement minimal...

Security Scan

This is an instruction-only TDD workflow that is internally consistent with its stated purpose; it asks for npm/git (reasonable) and contains testing patterns and git checkpoints but does not request secrets or install code.

Purpose & Capability

Name/description (TDD enforcing 80%+ coverage) aligns with the instructions and referenced patterns. Required binaries (npm, git) are appropriate for running tests and creating git checkpoints. No unexplained credentials, binaries, or config paths are requested.

Instruction Scope

SKILL.md gives explicit TDD steps (write tests, run npm test, commit at RED/GREEN, run coverage). It references unit/integration/E2E and includes mock examples for Supabase/Redis/OpenAI; these are illustrative. Caution: integration/E2E tests could be written to contact external services or databases in a real project, so inspect test code before running to avoid accidental production access.

Install Mechanism

No install spec and no code files are provided; the skill is instruction-only so it does not download or write artifacts to disk. This is the lowest-risk install posture.

Credentials

The skill itself does not request environment variables or credentials (none declared), which is proportional. However, real test suites in a repository may require DB/API credentials; the skill does not warn about that. Verify test runner configuration (package.json, test setup) and ensure tests run against isolated test/stub environments.

Persistence & Privilege

The skill is not always-enabled and does not request persistent presence or modify other skills. It instructs creating git commits in the local repo, which is expected behavior for a workflow tool.

Assessment

This skill appears to be what it says: a TDD workflow checklist and examples. Before you run it on a codebase: 1) review the repository's test files and package.json to see what npm test actually runs (look for scripts that run end-to-end tests or hit real services); 2) ensure tests run in an isolated test environment (use test databases, mock external APIs, or CI feature flags) so you don't leak or modify production data; 3) inspect any integration/E2E tests for hard-coded endpoints or credentials; 4) when running the workflow locally, confirm your git state and branch (the instructions create commits) or run in a disposable branch; 5) if you use CI, ensure secrets are scoped to test accounts. These precautions mitigate the main practical risk (accidentally running tests that talk to production systems), but the skill itself is coherent and non-malicious.

Test-Driven Development Workflow

Ensure all code development follows TDD principles with 80%+ code coverage.

When to Activate

• Writing new features or functionality
• Fixing bugs or issues
• Refactoring existing code
• User says "write tests", "add specs", "how should I test this"

Quick Start

1. Write user journey in acceptance-test format ("As a [role], I want...")
2. Generate test cases (happy path + edge cases + errors)
3. Run tests → verify RED state (must fail before implementation)
4. Implement minimal code to make tests pass → GREEN state
5. Refactor while keeping tests green
6. Verify 80%+ coverage achieved

Key Concepts

• Tests before code — Write tests first, then implementation
• RED-GREEN-REFACTOR — Fail → Pass → Improve (no exceptions)
• 80% coverage minimum — Unit, integration, and E2E combined
• Unit-level isolation — Mock dependencies, test behavior not implementation
• Independent tests — No test ordering dependencies; each can run solo

Common Usage

Most frequent patterns:

• Unit tests for functions and components
• Integration tests for API endpoints and database operations
• E2E tests for critical user flows
• Edge case and error path testing
• Fast execution (unit tests < 50ms each)

References

• references/workflow-steps.md — Detailed 7-step TDD cycle with git checkpoints
• references/patterns-and-best-practices.md — Test patterns, common mistakes, success metrics