Enforce a RED-GREEN-REFACTOR TDD workflow for software implementation tasks.
npx skills add https://github.com/josipmusa/jds --skill jds-tdd
Please help me install this Agent Skill. Skill: jds-tdd Source: https://github.com/josipmusa/jds/tree/main/skills/jds-tdd Command: npx skills add https://github.com/josipmusa/jds --skill jds-tdd
This skill enforces the RED-GREEN-REFACTOR TDD cycle during implementation, ensuring tests drive coding discipline and preventing post-hoc testing.
Start by writing a failing test for the new behavior, then implement the minimum code to pass, and refactor while keeping all tests green.
High-intent search queries and answers about installing and using this skill.
To enforce strict TDD cycles, you must explicitly adhere to the RED-GREEN-REFACTOR discipline, ensuring tests drive coding by requiring a failing test before any production code is written. This prevents post-hoc testing and maintains code quality.
The RED-GREEN-REFACTOR workflow is a test-driven development process where you first write a failing test (RED), implement the minimum code to pass it (GREEN), and then refactor the code while keeping all tests green. This enforces strict coding discipline.
To start implementing a feature with rigid TDD process enforcement, begin by writing a failing test for the new behavior. Then, implement the minimal code required to pass the test, and finish with a final refactoring pass to verify and clean up the production code.
No, you cannot write production code before tests in a strict TDD workflow. The process enforces a rule that code is written only after a failing test exists, ensuring that tests always precede implementation and driving code quality through formal cycle tracking.
Yes, TDD process enforcement applies to any feature development task where tests must precede production code. It tracks progress through a formal RED-GREEN-REFACTOR cycle, ensuring explicit adherence to testing discipline for every implementation task.
Test-driven development requires a final refactor pass to clean up and optimize the production code while ensuring all tests remain green. This step maintains code quality and verifies that the minimal implementation still functions correctly after structural improvements.
ChiejiGuide Red-Green-Refactor cycles with failing tests before implementation.
GainInsightDevAnalyze test coverage reports to identify untested code paths and gaps.
RektooooooExecute static analysis checks on Swift source files with xcodebuild and SourceKit.
GainInsightDevGenerate Markdown BDD scenarios from requirements with test type classification.
