skills.rest
thuyavan00
thuyavan00COMMUNITY
Explore all skills by this author →
GitHub

commit

Drafts git commit messages with conventional style and imperative mood from staged changes and diff reviews.

Updated Aug 15, 2025
Search Tags:#git#workflow#commit#version-control#conventional-commits#message-writing
One-click install
npx skills add https://github.com/thuyavan00/job-agent --skill commit-thuyavan00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/thuyavan00/job-agent/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/thuyavan00/job-agent --skill commit-thuyavan00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a structured git commit message that adheres to project conventions, reducing ambiguity and improving traceability.

Core Features & Use Cases

  • Analyze the current repository state (git status) and review recent changes (git diff, git log) to inform a precise, contextual commit message.
  • Draft a concise, imperative commit message that describes the "why" behind changes, and align it with the repository's conventions.
  • Stage and finalize the commit, optionally including a Co-Authored-By line to attribute contributors, with safeguards to avoid destructive actions.

Quick Start

Create a well-formed commit message for your latest changes by following the guided prompts.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a conventional commit message for staged changes?▼

To write a conventional commit message, analyze your staged changes via git diff and draft an imperative summary that explains the rationale behind the modifications to improve traceability and align with project conventions.

What is the best way to format git commit messages for better version control history?▼

The best way to format git commit messages is to use imperative mood and conventional-style messaging, ensuring the description explains why changes were made to maintain a clear and traceable version control history across repositories.

Does this approach support adding co-authorship metadata to a git commit?▼

Yes, this approach supports co-authorship metadata by optionally including a Co-Authored-By line in the commit message to attribute contributors, while applying safeguards to prevent destructive actions during the finalization process.

How do I ensure my commit message aligns with existing repository conventions?▼

To ensure alignment, the commit message is drafted based on a review of recent repository history via git log, matching the established conventions and standard git workflows already present in the project.

Can I use this workflow to analyze git status before finalizing a version control commit?▼

Yes, you can analyze the current repository state using git status and review recent diffs to inform a precise commit message before staging and finalizing the version control commit safely.

Related Skills

Explore More Software Engineering Skills→
jeremylongshorejeremylongshore
2.6k

generating-smart-commits

Generate conventional commit messages from staged Git changes.

Community
Basic
Soul-Brews-StudioSoul-Brews-Studio
116

release

Automate software releases with version bumps, changelogs, and GitHub releases.

Official
Advanced
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
BrunoAMSilvaBrunoAMSilva

git-commit

Generate Conventional Commits messages from repository diffs and stage files.

Community
Intermediate