git-commit

Identify session changes with git status and commit them using conventional messages.

4|Updated Oct 12, 2021
One-click install
npx skills add https://github.com/nicolasdao/puffy-core --skill git-commit-nicolasdao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/nicolasdao/puffy-core/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/nicolasdao/puffy-core --skill git-commit-nicolasdao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides you to create a clean, conventional commit message that reflects the session's changes, ensuring changelog-friendly history and reproducible work.

Core Features & Use Cases

  • Identify all modified and created files in the current session using git status --short and git diff --name-only.
  • Include only session-related changes in the commit by staging selected files and excluding pre-existing dirt.
  • Generate a single-line conventional commit message that follows the standard format and can be pushed to the repository's history.

Quick Start

Identify session changes using git status --short and git diff --name-only, then stage only those files and commit with a single-line conventional message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I commit only the files changed in my current session using a conventional commit message?

To commit only session changes, the skill identifies modified files using git status --short and git diff --name-only, stages those specific files while ignoring pre-existing dirt, and writes a single-line conventional commit message for a clean changelog history.

What is a session-aware conventional commit and how does it keep my git history clean?

A session-aware conventional commit isolates changes made during a specific working session, ignoring unrelated pre-existing dirt in the repository, and generates a single-line conventional commit message to ensure a clean and changelog-friendly history.

Can I generate changelog-friendly commit messages if my repository already has uncommitted changes?

Yes, you can generate changelog-friendly commit messages even with pre-existing dirt. The skill specifically determines your session changes using git diff and stages only those selected files, excluding unrelated modifications from the final commit.

What is the best way to stage only newly created files without including old modified files in git?

The best way to stage only new files is using a session-aware approach. The skill uses git status --short and git diff --name-only to determine your current session changes, stages only those files, and commits them with a conventional message.

Do I need to manually run git add before using a session-aware conventional commit tool?

No, you do not need to manually run git add. The skill automatically determines your session changes using git status --short, stages only the selected session files, and writes the single-line conventional commit message for you.

Why does my conventional commit include files I changed before the current session started?

Standard git commits include all staged files. This skill prevents that by using git diff --name-only to identify only current session changes, excluding pre-existing dirt to ensure your conventional commit message accurately reflects only the current work.