worktree-commit

Auto-committing changes in a git worktree with a task ID requires specifying the worktree path, request name, and task ID. The Skill stages all new, modified, and deleted files, fetches ticket data via MCP, and generates a Japanese commit message before committing.

Generating Japanese commit messages for worktree development is handled automatically by inferring ticket information from the branch name. It validates the worktree path and branch naming conventions, then uses the task ID and change details to create a standardized, auditable commit message in Japanese.

Staging all changes in a temporary worktree is automated by the Skill, which batches new, modified, and deleted files together. After validating the worktree path and branch naming, it stages all modifications before generating the commit message.

Fetching ticket data via MCP when committing worktree changes is supported as an optional step during the commit process. The Skill estimates ticket information from the branch name and can integrate related data fetched via MCP into the generated Japanese commit message.

Worktree-commit requires specific branch naming conventions to validate the worktree path and branch before staging changes. This validation ensures the task ID can be accurately estimated from the branch name for the standardized, auditable commit message generation.

Automating commits in a worktree-based development workflow eliminates manual commit operations and ensures consistent change history. It applies to scenarios where task completion requires a standardized, auditable commit containing a task ID and descriptive Japanese message.