commit

Enforce conventional commit guidelines for diffs and commit messages.

Updated Sep 6, 2018

Search Tags:#git #workflow #commit #diff #version-control #conventional-commits

Ready to run

npx skills add https://github.com/terakoya76/terakoya76-playbooks --skill commit-terakoya76

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/terakoya76/terakoya76-playbooks/tree/main/roles/dotfiles/files/claude/skills/commit
Command: npx skills add https://github.com/terakoya76/terakoya76-playbooks --skill commit-terakoya76

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain a consistent commit history by guiding you to diffs and commit messages that follow the conventional commits guidelines, avoiding co-authored or generated-by lines.

Core Features & Use Cases

Check diffs and prepare commits following conventional commits.
Enforce guidelines for commit messages during development workflow.
Use Case: when finishing a feature, run this skill to ensure the commit aligns with conventional commit rules before pushing.

Quick Start

Describe what you changed and commit using conventional commits guidelines.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I enforce conventional commits in my Git workflow?▼

To enforce conventional commits in Git, this Skill parses your diffs and guides you to form compliant commit messages. It checks your changes against guidelines before pushing.

What is a conventional commit message and how does it handle diffs?▼

A conventional commit message follows structured guidelines for types like features or bug fixes. This Skill parses your Git diffs to generate compliant messages automatically.

Can I use this for bug fixes and refactoring or only feature work?▼

You can use this for bug fixes, refactoring, and feature work. It applies conventional commit guidelines across daily development tasks to ensure commit history quality.

Does the conventional commit message include co-authored or generated-by lines?▼

No, conventional commit messages formed by this Skill avoid co-authored or generated-by lines. It strictly follows guidelines to keep your Git commit history clean.

What is the best way to prepare a commit from a diff using conventional commits?▼

The best way to prepare a commit is to describe what you changed. This Skill parses the diff and formats your input into a conventional commit message.

Why should I use conventional commits for version control?▼

You should use conventional commits for version control to maintain a consistent Git history. This Skill enforces guidelines by parsing diffs and avoiding co-authored lines.