zsp/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-03-30 13:43:26 +08:00
Code Issues Packages Projects Releases Wiki Activity

adjust: scope tdd checkpoints to active branch

Browse Source
This commit is contained in:
Toni Doni
2026-03-25 14:09:59 +03:00
parent fee93f2dab
commit 9cc5d085e1
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
skills/tdd-workflow/SKILL.md
View File

@@ -51,6 +51,9 @@ ALWAYS write tests first, then implement code to make tests pass.
- If the repository is under Git, create a checkpoint commit after each TDD stage - If the repository is under Git, create a checkpoint commit after each TDD stage
- Do not squash or rewrite these checkpoint commits until the workflow is complete - Do not squash or rewrite these checkpoint commits until the workflow is complete
- Each checkpoint commit message must describe the stage and the exact evidence captured - Each checkpoint commit message must describe the stage and the exact evidence captured
- Count only commits created on the current active branch for the current task
- Do not treat commits from other branches, earlier unrelated work, or distant branch history as valid checkpoint evidence
- Before treating a checkpoint as satisfied, verify that the commit is reachable from the current `HEAD` on the active branch and belongs to the current task sequence
- The preferred compact workflow is: - The preferred compact workflow is:
- one commit for failing test added and RED validated - one commit for failing test added and RED validated
- one commit for minimal fix applied and GREEN validated - one commit for minimal fix applied and GREEN validated
@@ -118,6 +121,7 @@ If the repository is under Git, create a checkpoint commit immediately after thi
Recommended commit message format: Recommended commit message format:
- `test: add reproducer for <feature or bug>` - `test: add reproducer for <feature or bug>`
- This commit may also serve as the RED validation checkpoint if the reproducer was compiled and executed and failed for the intended reason - This commit may also serve as the RED validation checkpoint if the reproducer was compiled and executed and failed for the intended reason
- Verify that this checkpoint commit is on the current active branch before continuing
### Step 4: Implement Code ### Step 4: Implement Code
Write minimal code to make tests pass: Write minimal code to make tests pass:
@@ -145,6 +149,7 @@ If the repository is under Git, create a checkpoint commit immediately after GRE
Recommended commit message format: Recommended commit message format:
- `fix: <feature or bug>` - `fix: <feature or bug>`
- The fix commit may also serve as the GREEN validation checkpoint if the same relevant test target was rerun and passed - The fix commit may also serve as the GREEN validation checkpoint if the same relevant test target was rerun and passed
- Verify that this checkpoint commit is on the current active branch before continuing
### Step 6: Refactor ### Step 6: Refactor
Improve code quality while keeping tests green: Improve code quality while keeping tests green:
@@ -156,6 +161,7 @@ Improve code quality while keeping tests green:
If the repository is under Git, create a checkpoint commit immediately after refactoring is complete and tests remain green. If the repository is under Git, create a checkpoint commit immediately after refactoring is complete and tests remain green.
Recommended commit message format: Recommended commit message format:
- `refactor: clean up after <feature or bug> implementation` - `refactor: clean up after <feature or bug> implementation`
- Verify that this checkpoint commit is on the current active branch before considering the TDD cycle complete
### Step 7: Verify Coverage ### Step 7: Verify Coverage
```bash ```bash