Commit

Generate Git commits with Conventional Commits format and signing.

786|79|Updated Jun 6, 2022
One-click install
npx skills add https://github.com/mihai-dinculescu/tapo --skill commit-mihai-dinculescu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Commit
Source: https://github.com/mihai-dinculescu/tapo/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/mihai-dinculescu/tapo --skill commit-mihai-dinculescu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of Git commits, ensuring adherence to project conventions and improving code history clarity.

Core Features & Use Cases

  • Enforces Conventional Commits: Automatically formats commit messages according to the <type>(<scope>): <description> standard.
  • Integrates Review & Changelog: Prompts users to run /review and /changelog commands before committing, ensuring code quality and documentation updates.
  • Secure Signing: Automatically signs commits using git commit -S for enhanced security.
  • Use Case: A developer finishes a new feature. They use this Skill to create a feat(api): add user profile endpoint commit, ensuring it's signed and follows the project's established format.

Quick Start

Use the commit skill to create a commit with the message "fix(deps): update all dependencies".

Frequently Asked Questions about Commit

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

FAQPage Schema
How do I create conventional commits in Git automatically?

Conventional commits are generated automatically by formatting messages into the `<type>(<scope>): <description>` structure, enforcing project conventions and improving code history clarity without manual formatting.

Can I sign Git commits using conventional commit messages?

Yes, Git commits are automatically signed using the `git commit -S` command, ensuring enhanced security and verified authorship while maintaining the conventional commit format.

How do I integrate code review and changelog generation before committing?

Code review and changelog generation are integrated by prompting users to run `/review` and `/changelog` commands before executing the commit, ensuring code quality and documentation updates.

What is the structure of a conventional commit message for version control?

A conventional commit message follows the `<type>(<scope>): <description>` standard, categorizing changes by type and scope to automate version control and changelog generation processes.

Do I need to confirm automated commit messages before execution?

Automated commit message confirmation is supported before execution, allowing developers to review and verify the generated conventional commit message prior to finalizing the Git commit.

When should I use conventional commits over standard Git commits?

Conventional commits should be used when you need to enforce project conventions, integrate automated changelog generation, and improve code history clarity through structured type and scope formatting.