commit

Create a single git commit with a conventional-commits message.

Updated May 23, 2026

Search Tags:#git #conventional commits #staging #code changes #commit message #branch context

Ready to run

npx skills add https://github.com/devturco/thiago-dev-template --skill commit-devturco

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/devturco/thiago-dev-template/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/devturco/thiago-dev-template --skill commit-devturco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns messy local changes into a single, well-written git commit message that follows your repository’s conventions.

Core Features & Use Cases

Staged, safe committing: Chooses relevant files from the current diff without staging .env, credentials, or secrets.
Style-matched messaging: Reads recent commit messages and branch context to write a conventional-commits message focused on the WHY.
One-shot commit workflow: Produces exactly one commit for the current working tree, reducing follow-up corrections.
Use Case: After refactoring a feature and updating a few related TypeScript files, generate a commit like a seasoned contributor rather than an ambiguous message.

Quick Start

Ask: "Commit these changes for me with a conventional message that explains the WHY, and end the message with Co-Authored-By: Claude [email protected]."

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate a conventional commit message from my current git diff?▼

To generate a conventional commit message from your git diff, the skill reads your current changes, recent commit history, and branch context to compose a single atomic commit focused on the WHY. It stages appropriate files automatically while avoiding secrets.

How do I stage code changes for a git commit without including .env or secrets?▼

Staging code changes without including .env files or secrets is handled automatically by reading the git status and diff to select relevant files. It avoids staging credentials and produces one safe, atomic commit for the working tree.

What is the best way to match a new commit message to my repository's recent style?▼

The best way to match a new commit message to your repository style is by reading recent commit history and branch context. The skill analyzes existing conventions to generate a conventional-commits message aligned with your project's established formatting.

Can I append a Co-Authored-By trailer to an automatically generated conventional commit?▼

Yes, you can append a Co-Authored-By trailer to an automatically generated conventional commit. You provide the desired trailer text as an argument, and the skill composes the final git commit message using a HEREDOC format that includes your specified details.

Does this tool create multiple commits for multiple staged files or just one atomic commit?▼

This tool creates exactly one atomic commit for your current working tree. It stages selected files from the diff and produces a single commit to encapsulate the changes, reducing the need for follow-up corrections.

Why should I use an automated commit message generator instead of writing git commit messages manually?▼

An automated commit message generator reads your code changes and branch context to produce style-matched conventional commits. This prevents ambiguous messages and ensures your commit history explains the reasoning behind the changes rather than just the actions taken.