commit

Creates git commits with compact imperative messages free of trailers and attribution.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/kbukum/gokit --skill commit-kbukum
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kbukum/gokit/tree/main/.github/skills/commit
Command: npx skills add https://github.com/kbukum/gokit --skill commit-kbukum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Commit histories often get cluttered with noisy messages containing Co-authored-by trailers, plan numbers, tool references, and review narration, making it hard for maintainers to understand what actually changed. This Skill enforces a clean, developer-friendly commit style for the gokit repository. ## Core Features & Use Cases - Focused staging discipline: Inspects staged versus unstaged changes with git status and git diff --cached, and splits mixed concerns into separate coherent commits. - Message conventions: Produces a single compact imperative subject line under ~72 characters, optionally matching Conventional Commit prefixes when the surrounding history uses them. - Strict exclusions: Never adds Co-authored-by trailers, plan/batch/PR numbers, or tool and session references, and never amends pushed history or runs destructive git commands. - Use Case: After finishing a bug fix in the gokit di module, ask for a commit and receive a message like "Rename Resolve to MustResolve in di container" with nothing extra attached. ## Quick Start Ask the assistant to commit your staged changes in the gokit repository with a clean message describing what changed.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a clean git commit message?▼

Write a single imperative subject line under about 72 characters that states what changed, such as "Add fix-reviews skill". Add a short body only when the reason for the change is not obvious from the subject.

How to commit staged changes in git from the command line?▼

Stage specific paths with git add, verify with git status --short and git diff --cached, then run git commit -m with your subject line. For a subject plus body, use git commit -F with a message file.

Should commit messages include Co-authored-by trailers?▼

This Skill never includes Co-authored-by trailers or any other attribution, plan numbers, or tool references. The goal is a message that reads as if a maintainer wrote it, with no process narration.

When should I use Conventional Commit prefixes like feat or fix?▼

Use prefixes like feat:, fix:, or docs: only when the surrounding repository history already uses them. Match the existing style rather than forcing a convention onto a repo that does not follow one.

Can this Skill amend or rewrite pushed commits?▼

No. It never amends or rewrites already-pushed history and never runs destructive git commands on uncommitted work. It only pushes when explicitly asked or when the task requires the commit on the branch.