commit

Create local git commits with conventional commit message formatting.

Updated Jul 8, 2026

Search Tags:#automation #git #developer tools #version control #commit

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/missdeer/skills/tree/main/commit
Command: npx skills add https://github.com/missdeer/skills --skill commit-missdeer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction of manual git commit formatting and ensures that every local commit adheres strictly to repository conventions without requiring manual intervention for style checks.

Core Features & Use Cases

Conventional Formatting: Automatically structures commit messages following standard type(scope): subject patterns.
Safety-First Workflow: Performs pre-commit inspections of the repository state and handles GPG signing failures gracefully.
Use Case: When you have finished a feature and want to commit your changes, this skill will analyze your staged files, draft a compliant message, and execute the commit command while ensuring no sensitive files are accidentally included.

Quick Start

Ask the assistant to commit these changes to the repository using the standard conventions.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automate conventional commit messages for git?▼

To automate conventional commit messages, this skill analyzes your staged repository state and drafts a compliant type(scope): subject message before executing the local git commit. It enforces standard formatting without manual style checks.

What is the best way to ensure my local git commits follow project conventions?▼

The best way to ensure local git commits follow project conventions is using an automated skill that inspects repository state and structures commit messages following standard type(scope): subject patterns, eliminating manual formatting friction.

Do I need git CLI access to automate conventional commit formatting?▼

Yes, you need git CLI access and local file system permissions to automate conventional commit formatting. The skill requires these to write temporary commit message files and execute the commit command safely.

Can automated git commits handle GPG signing failures gracefully?▼

Automated git commits can handle GPG signing failures gracefully through safety-first pre-commit inspections. The skill performs repository state checks before attempting the local commit to manage these edge cases.

How does automated commit formatting prevent sensitive files from being committed?▼

Automated commit formatting prevents sensitive file inclusion by performing pre-commit inspections of the repository state. It analyzes staged files to ensure no sensitive data is accidentally committed before executing the git commit command.

When should I not use automated conventional commit tools?▼

You should not use automated conventional commit tools for multi-commit squashing or remote repository pushes, as this skill is designed strictly for creating single local git commits and analyzing staged file states.