Enforce test-first delivery with failing tests before implementation and 80 percent coverage.
npx skills add https://github.com/WUIX69/e-lock --skill tdd-workflow-wuix69
Please help me install this Agent Skill. Skill: tdd-workflow Source: https://github.com/WUIX69/e-lock/tree/main/.agent/.agents/skills/tdd-workflow Command: npx skills add https://github.com/WUIX69/e-lock --skill tdd-workflow-wuix69
This Skill prevents fragile, untested code changes by forcing a test-first workflow for features, bug fixes, and refactors, so implementation stays safe and predictable.
Use the tdd-workflow skill to plan the change with failing tests first, then implement the code until all tests pass and coverage reaches the required threshold.
High-intent search queries and answers about installing and using this skill.
Test-first development is enforced by requiring failing tests before implementation. This workflow applies to new features, bug fixes, and refactors, ensuring expected behavior is defined clearly before code changes are made.
Maintaining code coverage during refactoring requires validating edge cases and verifying coverage thresholds. The workflow enforces 80 percent or higher coverage, keeping logic changes safe and outcomes verifiable while preventing fragile code.
Writing failing tests for API endpoints and UI components involves defining expected behavior before implementation. This test-first approach covers unit, integration, and E2E scenarios, validating boundaries and errors across critical browser workflows.
Yes, this test-driven development workflow supports unit, integration, and E2E testing. It applies to critical browser workflows and API endpoints, requiring failing tests before implementation and ensuring 80 percent or higher coverage verification.
Test-first delivery prevents fragile code changes by forcing a test workflow before implementation. This makes software changes predictable and safe by defining expected behavior upfront and requiring comprehensive edge-case validation.
Failing tests before implementation are needed when adding API endpoints, building UI components, refactoring logic, or stabilizing regressions. This test-first workflow ensures 80 percent or higher coverage and edge-case validation across all software changes.
DRMacIverAutomate a disciplined feature-implementation workflow with test-first development and runtime validation.
LuohaothuAnalyze coverage reports and flag files below the 80% threshold.
Objective-ArtsAutomate software development from planning through coding, quality gating, and verification.
iCesofTApply Behavior-Driven Development patterns with Given-When-Then scenarios and feature files.
