skills.rest
AnthonyPoschen
AnthonyPoschenCOMMUNITY
Explore all skills by this author →
GitHub

git-commit-workflow

Create small, reviewable Git commits with descriptive messages and AI assistance trailers.

2|Updated May 14, 2026
Search Tags:#git#workflow#code review#version control#commit#staging#commit message
One-click install
npx skills add https://github.com/AnthonyPoschen/agent-skills --skill git-commit-workflow-anthonyposchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-workflow
Source: https://github.com/AnthonyPoschen/agent-skills/tree/main/skills/git-commit-workflow
Command: npx skills add https://github.com/AnthonyPoschen/agent-skills --skill git-commit-workflow-anthonyposchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dirty worktrees and mixed changes often lead to oversized, unclear commits that are hard to review, revert, or test. This Skill turns uncommitted work into a sequence of small, logically separated commits with clear messages and an explicit AI assistance trailer. ## Core Features & Use Cases - Logical Commit Splitting: Inspects staged and unstaged diffs, groups changes into independent units, and stages only the files belonging to each commit. - Descriptive Commit Messages: Writes concise imperative subjects, optional bodies for non-obvious rationale, and an Assisted-by trailer for AI-authored changes. - Safety Guardrails: Never discards or rewrites user changes, leaves unrelated work unstaged, and only pushes or opens PRs when explicitly asked. - Use Case: After finishing a refactoring phase, the Skill inspects the worktree, separates the refactor from unrelated formatting changes, commits each group with a clear message, and reports the resulting hashes. ## Quick Start Ask the agent to review the current worktree and split the pending changes into logical commits with descriptive messages.

Frequently Asked Questions about git-commit-workflow

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

FAQPage Schema
How do I split staged changes into multiple commits?▼

Inspect the staged diff with git diff --cached, identify independent logical groups, then unstage and re-stage each group separately before committing. Each commit should contain one coherent unit that can be reviewed, tested, and reverted on its own.

How to write a good Git commit message?▼

Write one short imperative subject line stating the concrete change, ideally under 72 characters with no trailing period. Add a body only for non-obvious reasons, risks, or validation evidence, and follow the repository's existing convention when one exists.

When should changes be kept in one commit instead of split?▼

Keep changes together when splitting would leave either commit broken, unreviewable, or missing the tests that explain the behavior. A feature and its focused tests usually belong in the same commit.

Does this workflow amend or rebase existing commits?▼

No. The workflow never amends, rebases, squashes, or rewrites history unless the user explicitly requests it. It also never discards or overwrites uncommitted user changes.

What is the Assisted-by trailer in a commit message?▼

It is a Git trailer appended at the end of AI-authored or AI-assisted commit messages, formatted as Assisted-by: <agent>/<model>, such as Assisted-by: Codex/GPT-5. It records that AI tooling contributed to the change.

Related Skills

Explore More Software Engineering Skills→
tachiiri-orgtachiiri-org

implement-py

Plan and implement Python code changes with ruff, pyright, and pytest validation.

Official
Advanced
Chorus-AIDLCChorus-AIDLC
1.1k

pr-workflow

Automate pull request workflows with git and the GitHub CLI.

Official
Intermediate
owenlamontowenlamont
1

python-lint-format

Automate Python code linting and formatting with pre-commit hooks.

Community
Advanced
cstrahancstrahan

git-rebase-interactive

Automate programmatic interactive rebases for git history cleanup and commit hygiene.

Community
Advanced