skills.rest
Marshall-Hallenbeck
Marshall-HallenbeckCOMMUNITY
Explore all skills by this author →
𝕏@mjhallenbeckGitHub

commit

Group session-modified files into conventional Git commits with granular patching.

5|1|Updated Oct 18, 2019
Search Tags:#automation#git#workflow#version control#commit#conventional commits
One-click install
npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill commit-marshall-hallenbeck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Marshall-Hallenbeck/dot_files/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill commit-marshall-hallenbeck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of messy, unorganized Git history by automatically grouping session-specific changes into logical, conventional commits.

Core Features & Use Cases

  • Session-Aware Grouping: Automatically identifies files modified during the current session to ensure only relevant work is committed.
  • Granular Patching: Allows staging specific hunks of code when a file contains both session-related and unrelated changes.
  • Conventional Commit Compliance: Enforces structured commit messages with traceability for PRs, Sentry issues, and GitHub issues.

Quick Start

Run the commit skill to automatically group your current session changes and commit them with a descriptive message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commits for my current git workflow?▼

Automate conventional commits by grouping session-specific file modifications into logical, structured commit messages. This ensures clean git history and traceability for PRs and GitHub issues without manual message formatting.

What is the best way to group session-specific changes into a clean Git history?▼

Group session-specific changes by identifying files modified during your current working session and staging them together. This approach creates logical, conventional commits that maintain a clean and traceable version control history.

Can I stage partial file changes or specific code hunks for a commit?▼

Yes, you can stage specific hunks of code. Granular patching allows staging partial file changes when a file contains both session-related and unrelated modifications, applying standard diff-filtering utilities to manage the working-tree state.

Do I need any specific dependencies or utilities to manage automated git commits?▼

You need git and standard diff-filtering utilities installed in your environment. These dependencies are required to manage your working-tree state, apply granular patches, and automate the commit workflow.

How does conventional commit compliance handle traceability for issues and PRs?▼

Conventional commit compliance enforces structured commit messages that include traceability metadata for PRs, Sentry issues, and GitHub issues. This links your version control history directly to your project management and error tracking systems.

Related Skills

Explore More Software Engineering Skills→
t-miura-024t-miura-024

mt-check-git-diff

Analyze git repository changes and retrieve detailed diffs for modified files.

Community
Intermediate
guicauladaguicaulada
1

create-pr

Create GitHub pull requests with auto-generated titles and descriptions from branch commits.

Community
Advanced
AmidVoshakulAmidVoshakul

commit

Create conventional git commit messages with issue references and branch safety checks.

Community
Intermediate
yoshihiko555yoshihiko555

commit

Stage and commit only files discussed in the conversation.

Community
Advanced