skills.rest
first-fluke
first-flukeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

commit

Format and validate git commits against the Conventional Commits specification.

218|33|Updated Jan 7, 2026
Search Tags:#automation#git#commit#conventional-commits#branch-naming#co-authored-by
One-click install
npx skills add https://github.com/first-fluke/fullstack-starter --skill commit-first-fluke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/first-fluke/fullstack-starter/tree/main/.agent/skills/commit
Command: npx skills add https://github.com/first-fluke/fullstack-starter --skill commit-first-fluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create git commits that conform to the Conventional Commits specification and apply project-specific branch naming rules, reducing ambiguity and enabling automatic changelog generation.

Core Features & Use Cases

  • Enforces conventional commit types (feat, fix, docs, chore, etc.) and optional scopes.
  • Applies project-specific branch prefixes (feature/, fix/, chore/, docs/) to new branches.
  • Supports Co-Authored-By metadata and automated templates for consistent messages across teams.

Quick Start

Use the /commit command to generate a conventional commit message for a feature update on a feature branch, e.g. feat(auth): add login retry, Co-Authored-By: Jane Doe [email protected].

Frequently Asked Questions about commit

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

FAQPage Schema
How do I format conventional commits for multiple modules in git?▼

Conventional commits for multiple modules are formatted by enforcing commit types like feat or fix, adding an optional scope, and structuring the message to reduce ambiguity across your project.

What is the best way to automate branch naming rules in a git workflow?▼

Automating branch naming rules involves applying project-specific prefixes like feature/ or fix/ to new branches, ensuring consistent tracking across feature, fix, or chore changes.

How do I add Co-Authored-By metadata to automated commit messages?▼

Co-Authored-By metadata is added to automated commit messages by applying structured templates that append contributor information, ensuring consistent attribution across team workflows.

Can I integrate conventional commit validation into a pre-commit or CI workflow?▼

Conventional commit validation can be integrated into pre-commit or CI workflows to enforce message structure, validate branch prefixes, and support automatic changelog generation.

Does this commit standardization approach work without additional git dependencies?▼

This commit standardization approach works without additional dependencies, formatting and validating git commits directly to conform to the Conventional Commits specification.

Related Skills

Explore More Software Engineering Skills→
Utchash007Utchash007

commit

Stage git changes and generate conventional commit messages with confirmation.

Community
Advanced
edfentonedfenton
3

shared-changelog

Generate CHANGELOG.md from Git history using conventional commits.

Community
Advanced
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
dbensmithdbensmith

make-repo-contribution

Validate contributions against repository-specific guidelines and templates.

Community
Advanced