skills.rest
morodomi
morodomiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tdd-commit

Stage changes, run pre-commit checks, and commit with a conventional message.

8|2|Updated Oct 28, 2025
Search Tags:#git#workflow#tdd#commit#pre-commit#cycle-management
One-click install
npx skills add https://github.com/morodomi/tdd-skills --skill tdd-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-commit
Source: https://github.com/morodomi/tdd-skills/tree/main/plugins/tdd-core/skills/tdd-commit
Command: npx skills add https://github.com/morodomi/tdd-skills --skill tdd-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill completes the TDD cycle by performing the final commit phase, ensuring changes are captured and the cycle moves forward after a REVIEW.

Core Features & Use Cases

  • Finalize the TDD cycle by staging changes, validating with pre-commit checks, and creating a clear, conventional commit message.
  • Update cycle documentation and status to DONE to keep the team aligned and traceable.
  • Use Case: After successful PLAN/RED/GREEN/REFACTOR/REVIEW steps, run tdd-commit to lock in changes and prepare for the next phase (e.g., push or onboard new tasks).

Quick Start

Review changes with git status, stage them with git add, create a descriptive commit message following the Type format (feat/fix/refactor/test), and push to trigger the next cycle.

Frequently Asked Questions about tdd-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commits at the end of a TDD cycle?▼

To automate git commits at the end of a TDD cycle, this skill stages changes, runs pre-commit checks, generates a conventional commit message, and marks the cycle status as done.

What is the best way to generate conventional commit messages after a TDD review?▼

The best way to generate conventional commit messages after a TDD review is using an automated workflow that applies the Type format, such as feat, fix, refactor, or test, to your staged changes.

How does a pre-commit check integrate with a TDD workflow?▼

A pre-commit check integrates with a TDD workflow by validating staged changes before finalizing the cycle, ensuring code quality and verification are met before the commit message is created.

Do I need to manually update cycle documentation after staging changes?▼

No, you do not need to manually update cycle documentation after staging changes; this skill automatically updates the cycle status to done and aligns documentation for the next phase.

When should I run a TDD commit automation in my development cycle?▼

You should run a TDD commit automation after successfully completing the plan, red, green, refactor, and review steps, locking in changes to prepare the project for the next cycle or push.

Related Skills

Explore More Software Engineering Skills→
Sumeet138Sumeet138
1

workflow-patterns

Enforce a TDD workflow with RED-GREEN-REFACTOR steps and git commit protocols.

Community
Advanced
bdsqqqbdsqqq
59

git-ship

Stage modified files, commit with conventional commits, and push to the remote repository.

Community
Intermediate
chijunzhengchijunzheng

tdd-committer

Verify tests, stage files, and create conventional commits in Git.

Community
Advanced
dudusoardudusoar

git-log

Generate Conventional Commits messages and update GIT_LOG.md documentation.

Community
Basic