git-commit

Create standardized git commits with Task IDs from branch names or user input.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/taptap/agents-plugins --skill git-commit-taptap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/taptap/agents-plugins/tree/main/plugins/git/skills/commit
Command: npx skills add https://github.com/taptap/agents-plugins --skill git-commit-taptap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of consistent, traceable git commit messages by extracting Task IDs from branch names or user input, enforcing required changelog and impact sections, and reducing manual formatting errors during everyday commits.

Core Features & Use Cases

  • Automatic Task ID Extraction: Pulls TAP-123 style IDs from the current branch or prompts the user for a task link or ID.
  • Branch and Commit Flow Management: Detects default branches, helps create feature branches when needed, and decides whether to create a new branch before committing.
  • Conventional Commit Generation: Analyzes diffs to determine commit type (feat/fix/refactor/etc.), generates a structured commit message including changelog and impact sections, stages files, and executes the commit.
  • Use Case: A developer who types a natural request to commit changes can receive a properly formatted commit message that links to the task and adheres to repository conventions.

Quick Start

Ask the git-commit skill to create a standardized commit that extracts the task ID from your branch and generates a complete commit message with changelog and impact sections.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I create a git commit message that automatically includes a task ID?

No, this skill does not require external dependencies. It operates autonomously to analyze your local staged and unstaged file diffs to determine the appropriate conventional commit type and required sections.

What's the best way to enforce conventional commit formats with changelog and impact sections?

The best way to enforce conventional commit formats is to automate diff analysis for commit type determination, generating a structured commit message that validates required changelog and impact sections before execution.

Can I use this to create a feature branch and prepare changes before committing?

Yes, you can use this to manage your commit flow. It detects default branches and helps create feature branches when needed, deciding whether to branch before staging files and executing the commit.

Why does my automated commit workflow fail to link the task ID to the branch name?

Task ID linking fails if the identifier is absent from the branch name. This skill solves extraction failures by prompting for a task link or ID during commit message generation to ensure traceability.