git-commit

Use when: create a conventional git commit from the current diff with logical staging and message analysis.

Repository: kimtth/agent-skill-100-lines-or-less
Last source activity: May 22, 2026 at 12:33
Detected SKILL.md language: English
Stars: 2
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/kimtth/agent-skill-100-lines-or-less --skill git-commit

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

academic-paper-review

Use when: review an academic paper with a structured review form and multiple reviewer personas.

2026-06-26

api-design

Use when: design a clear, consistent, and evolvable API contract before implementing it.

2026-06-26

architecture-decision-records

Use when: record a significant technical decision, its context, and consequences as an ADR.

2026-06-26

View all from this repository

name	git-commit
description	Use when: create a conventional git commit from the current diff with logical staging and message analysis.

Goal: create one clear commit that matches the actual change.

Use for:

"commit this", "write a commit message", or /commit
grouping related file changes
generating Conventional Commit messages from a diff

Workflow:

Inspect git status --short and the relevant diff.
Separate unrelated user changes from this task's changes.
Stage only the intended logical group.
Choose type and optional scope from the diff.
Write an imperative subject under 72 chars, ideally under 50.
Add a body only when the reason is not obvious.
Commit only after explicit user approval.

Types:

feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert

Message shape:

<type>(<scope>): <imperative summary>

<body only when useful>

Rules:

do not stage unrelated changes
do not include secrets or generated noise
do not commit without the user's clear request
mention tests or verification in the body only when relevant

git-commit

Source facts

Install options

Review the source files

More from this repository

More from this repository