tdd-committer

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

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/chijunzheng/ShowMe --skill tdd-committer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-committer
Source: https://github.com/chijunzheng/ShowMe/tree/main/.claude/skills/tdd-committer
Command: npx skills add https://github.com/chijunzheng/ShowMe --skill tdd-committer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the post-feature workflow by verifying tests, staging changes, and creating meaningful commits with conventional messages.

Core Features & Use Cases

  • Automated test verification: Checks that all tests pass before committing.
  • Smart staging: Stages only relevant, feature-related files to keep history clean.
  • Conventional commits: Generates standardized commit messages and tracks progress.
  • Progress tracking: Updates a progress log with commit references for auditability.

Quick Start

Instruct the agent to verify tests, stage relevant files, generate a conventional commit message, and commit changes after all tests pass.

Frequently Asked Questions about tdd-committer

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

FAQPage Schema
How do I automate git commits only after tests pass in a TDD workflow?

To automate git commits in a TDD workflow, you can use a tool that verifies all tests pass, automatically stages relevant modified files, and generates a conventional commit message to ensure a clean history.

What is the best way to enforce conventional commit messages automatically?

The best way to enforce conventional commit messages automatically is by integrating a commit automation tool that generates standardized messages and tracks feature progress with commit references.

How does smart staging keep git history clean during feature development?

Smart staging keeps git history clean by selectively staging only relevant, feature-related modified files instead of all changes, ensuring commits remain focused and meaningful within the development cycle.

Can I track feature progress automatically alongside git commits?

Yes, you can track feature progress automatically by updating a progress log with commit references during the automated commit process, providing auditability for your TDD workflow.

Does automated test verification block commits when tests fail?

Automated test verification blocks commits when tests fail by enforcing a strict check that all tests must pass before proceeding to stage modified files and create the commit.

When should I not use automated TDD commit workflows?

You should not use automated TDD commit workflows when you need to stage unrelated changes, bypass test verification for hotfixes, or manually craft non-conventional commit messages for specific audit requirements.