Git Commit
Use when user asks to commit changes, mentions "/commit", "commit message", or stages changes - conventional commit message generation from diff, type/scope auto-detection, intelligent staging, git safety
Install
npx skills add PanPanFR/oh-my-openkilo --skill git-commitgit clone --depth 1 https://github.com/PanPanFR/oh-my-openkilo.git /tmp/oh-my-openkilo
mkdir -p ~/.claude/skills
cp -r /tmp/oh-my-openkilo/skills/git-commit ~/.claude/skills/git-commitPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Git Commit with Conventional Commits
Create standardized semantic commits. Analyze the actual diff to determine type, scope, and message. Terse, exact, no fluff.
## Format
```
<type>(<optional scope>): <description>
[optional body]
[optional footer(s)]
```
## Rules
**Subject line:**
- `<type>(<scope>): <imperative summary>` (scope optional)
- Types: `feat`, `fix`, `refactor`, `perf`, `docs`, `test`, `chore`, `build`, `ci`, `style`, `revert`
- Imperative mood: "add", "fix", "remove" (not "added", "adds", "adding")
- <=50 chars preferred, hard cap 72
- No trailing period
- Lowercase after colon unless project convention requires otherwise
**Body (only if needed):**
- Skip entirely when subject is self-explanatory
- Include body only for: non-obvious *why*, breaking changes (`feat!: ...` or `BREAKING CHANGE:`), migration notes, linked issues
- Bullets `-` not `*`
- Reference issues at end: `Closes #123`, `Refs #456`
**What NEVER goes in:**
- Conversational filler ("This commit does X", "I", "we", "now")
- AI attribution or generated markers
- Restating file names when scope already says it
## Workflow
1. **Analyze diff:** `git diff --staged` (staged) or `git diff`; check `git status --short`
2. **Stage if needed:** `git add path/to/file`, patterns (`git add *.test.*`), or `git add -p`. **Never commit secrets** (.env, credentials.json, private keys)
3. **Generate message:** type + scope from diff; description = imperative, <=50 chars
4. **Commit:**Details
- Skill name
git-commit- Repository
- PanPanFR/oh-my-openkilo
- Path
skills/git-commit/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
FAQ
What does the Git Commit skill do?
Use when user asks to commit changes, mentions "/commit", "commit message", or stages changes - conventional commit message generation from diff, type/scope auto-detection, intelligent staging, git safety
How do I install the Git Commit skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add PanPanFR/oh-my-openkilo --skill git-commit. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Git Commit popular?
It lives in PanPanFR/oh-my-openkilo, which has 9 GitHub stars and 1 forks.
Related skills
Adaptive
9PanPanFR/oh-my-openkilo
Instructions to make or update an app's UI so that it adapts to different Android devices including phones, tablets, foldables, laptops, desktop, TV, Auto, and XR. It includes how to handle different window sizes, pointing devices (such as mouse) and text entry devices (such as keyboard) using the Compose MediaQuery API, and how to preserve UI, navigation, scroll, and media playback state across configuration changes (such as folding/unfolding a foldable, rotating a device, or resizing a window). It also covers multi-pane layouts using Navigation3 Scenes, adaptive UI components (such as button
Agentmemory
9PanPanFR/oh-my-openkilo
Index for agentmemory internals: how it is wired into a host agent, its architecture and ports, configuration flags, capture hooks, MCP tool surface, and REST fallback. Use when installing or debugging agentmemory itself, when a memory tool name or parameter is unclear, or when capture is not recording. For normal recall and save work, use agentmemory-ops instead.
Agentmemory History
9PanPanFR/oh-my-openkilo
Read past work: resume the last session, recap recent sessions, list agent-linked commits, trace a line back to the session that wrote it, or compact the current conversation for handoff. Use when the user says "where were we", "resume", "recap", "session history", "what did we do", "why is this code here", "who wrote this", or "handoff".
Artifact Hygiene
9flurdy/agent-skills
Run a local-only, read-only advisory audit of publishable working-tree files and unpublished branch history with redaction-safe findings.
Code Review
9PanPanFR/oh-my-openkilo
Use when reviewing a branch, PR, diff, or work-in-progress changes - two-axis review of coding standards compliance and spec fidelity with concise actionable findings
Beads Setup
9flurdy/agent-skills
Preview and separately confirm a fresh repository Beads store with a dedicated private GitHub Dolt remote. Refuses existing state; keeps initialization, creation, and first publication individually gated.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.