What documentation does it update?

It updates the individual TDD cycle document to a 'DONE' status and refreshes the 'docs/STATUS.md' file to reflect the latest project progress.

Will it run my tests before committing?

It checks for existing pre-commit hooks in your repository to ensure tests run automatically; otherwise, it relies on the validation performed in the previous tdd-review phase.

Does this skill follow Git commit standards?

Yes, it uses the Conventional Commits format (feat, fix, refactor, test) and adds AI attribution via Co-Authored-By tags.

How do I trigger the commit phase?

You can trigger this skill by typing 'commit' or 'コミットして' in the Claude Code terminal after finishing your code review.

TDD Commit Phase

Name: TDD Commit Phase
Author: morodomi

bymorodomi

Developer Tools

Finalizes the TDD cycle by validating changes, updating documentation, and executing Git commits using standardized conventions.

About

The tdd-commit skill is the final stage of the Question-Driven TDD workflow for Claude Code. It automates the transition from a completed code review to a finalized Git commit by verifying changes, checking for pre-commit hooks, and updating project-wide status documentation. By enforcing structured commit messages and ensuring cycle logs are marked as complete, it helps maintain a high-integrity repository history and consistent project tracking without manual overhead.

Key Features

Automatic updates to cycle documentation and docs/STATUS.md files
0 GitHub stars
Pre-commit hook verification to ensure final code integrity
Seamless transition between TDD phases from REVIEW to DONE
Summarized change verification via git status and git diff
Automated Conventional Commit message generation including Co-Authored-By metadata

Use Cases

Maintaining an accurate project status and history log automatically
Closing out TDD cycles with verified, documented code changes
Enforcing consistent Git commit conventions across a project

About

Key Features

Automatic updates to cycle documentation and docs/STATUS.md files
0 GitHub stars
Pre-commit hook verification to ensure final code integrity
Seamless transition between TDD phases from REVIEW to DONE
Summarized change verification via git status and git diff
Automated Conventional Commit message generation including Co-Authored-By metadata

Use Cases

Maintaining an accurate project status and history log automatically
Closing out TDD cycles with verified, documented code changes
Enforcing consistent Git commit conventions across a project