How do I install the Git Commit Assistant skill?

Run npx skillmds@latest add fubira/git-commit-assistant in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Commit Assistant safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Commit Assistant?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Commit Assistant free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Commit Assistant?

fubira (@fubira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Commit Assistant by fubira — Agent Skill

Name: Git Commit Assistant
Rating: 4.5 (4 reviews)
Author: fubira

Git Commit Assistant

Stages and commits changes safely in any repository. Use when the user asks to commit, or when a commit would include untracked or sensitive files (credentials, MCP configs, personal settings). Writes Conventional Commits messages with a Japanese explanation. Do not use to merely inspect git status or a diff.

fubira Updated Sep 10, 2026

File contents

Git Commit Assistant Skill

Safe, high-quality Git commits. Sensitive file exclusion, .gitignore management, Conventional Commits message generation.

Activation Triggers

"commit", ".gitignore", push-related requests

Workflow

Phase 1: Repository Analysis

git status --porcelain + git branch --show-current to check state
Read .gitignore, suggest missing required patterns

Phase 2: File Classification

AUTO_EXCLUDE (never commit):

Secrets: *.key, *.pem, *credentials*, *secret*, *password*, .env*
MCP config: .claude.json, .mcp.json*
Personal settings: settings.json, settings.local.json, IDE configs
Build artifacts: node_modules/, dist/, build/, vendor/, *.log, *.cache
OS: .DS_Store, Thumbs.db

AUTO_COMMIT (generally safe):

Source code (src/**, internal/**, lib/**), tests, docs (*.md)
Shared config (.gitignore, package.json, tsconfig.json, go.mod, .github/workflows/*)
Skills (~/.claude/skills/**)

CONFIRM (user decision): Files > 1MB, new directories, executables, unclassified config files

Phase 3: Commit Message Generation

Analyze changes from git diff --cached and git status
Generate Conventional Commits message:
```
<type>(<scope>): <subject>  ← English, max 50 chars, imperative

- <description (Japanese OK)>
```
- 3-5 bullets explaining what/why/impact. No file lists
- Attribution trailer comes from attribution.commit in settings.json — do not write it manually
Confirm with the user only when Phase 2 turned up a CONFIRM-class file, a file that should be excluded, or an ambiguous commit scope. Invoking this skill already expresses intent to commit, so an unambiguous commit proceeds without a separate approval step.

Phase 4: Commit & Push

Stage with git add / git rm
Commit using heredoc, verify success
Push only after user confirmation

Sensitive Content Scan

Scan diff before commit:

API keys: [A-Za-z0-9_-]{20,}
Passwords: password.*=.*
URLs with credentials: ://.*:.*@

Warn and abort commit on detection.

Error Handling

Error	Action
Merge conflict	Prompt resolution, show conflict files
Detached HEAD	Suggest `git switch -c <branch>`
Nothing to commit	Report clearly

Supporting Files

templates/commit-message.md: Message template and examples

---name: git-commit-assistantdescription: Stages and commits changes safely in any repository. Use when the user asks to commit, or when a commit would include untracked or sensitive files (credentials, MCP configs, personal settings). Writes Conventional Commits messages with a Japanese explanation. Do not use to merely inspect git status or a diff.---# Git Commit Assistant SkillSafe, high-quality Git commits. Sensitive file exclusion, .gitignore management, Conventional Commits message generation.## Activation Triggers- "commit", ".gitignore", push-related requests## Workflow### Phase 1: Repository Analysis1. `git status --porcelain` + `git branch --show-current` to check state2. Read `.gitignore`, suggest missing required patterns### Phase 2: File Classification**AUTO_EXCLUDE (never commit)**:- Secrets: `*.key`, `*.pem`, `*credentials*`, `*secret*`, `*password*`, `.env*`- MCP config: `.claude.json`, `.mcp.json*`- Personal settings: `settings.json`, `settings.local.json`, IDE configs- Build artifacts: `node_modules/`, `dist/`, `build/`, `vendor/`, `*.log`, `*.cache`- OS: `.DS_Store`, `Thumbs.db`**AUTO_COMMIT (generally safe)**:- Source code (`src/**`, `internal/**`, `lib/**`), tests, docs (`*.md`)- Shared config (`.gitignore`, `package.json`, `tsconfig.json`, `go.mod`, `.github/workflows/*`)- Skills (`~/.claude/skills/**`)**CONFIRM (user decision)**: Files > 1MB, new directories, executables, unclassified config files### Phase 3: Commit Message Generation1. Analyze changes from `git diff --cached` and `git status`2. Generate Conventional Commits message: ``` <type>(<scope>): <subject> ← English, max 50 chars, imperative - <description (Japanese OK)> ``` - 3-5 bullets explaining what/why/impact. No file lists - Attribution trailer comes from `attribution.commit` in settings.json — do not write it manually3. Confirm with the user only when Phase 2 turned up a CONFIRM-class file, a file that should be excluded, or an ambiguous commit scope. Invoking this skill already expresses intent to commit, so an unambiguous commit proceeds without a separate approval step.### Phase 4: Commit & Push1. Stage with `git add` / `git rm`2. Commit using heredoc, verify success3. Push only after user confirmation## Sensitive Content ScanScan diff before commit:- API keys: `[A-Za-z0-9_-]{20,}`- Passwords: `password.*=.*`- URLs with credentials: `://.*:.*@`Warn and abort commit on detection.## Error Handling| Error | Action ||-------|--------|| Merge conflict | Prompt resolution, show conflict files || Detached HEAD | Suggest `git switch -c <branch>` || Nothing to commit | Report clearly |## Supporting Files- `templates/commit-message.md`: Message template and examples

Frequently asked questions