skills.rest
fubira
fubiraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit-assistant

Analyze git status and .gitignore to classify files and generate Conventional Commit messages.

1|Updated Nov 2, 2025
Search Tags:#git#security#commit#code-quality#gitignore#conventional-commits
One-click install
npx skills add https://github.com/fubira/claude-code-settings --skill git-commit-assistant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-assistant
Source: https://github.com/fubira/claude-code-settings/tree/main/skills/git-commit-assistant
Command: npx skills add https://github.com/fubira/claude-code-settings --skill git-commit-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps you classify changes, manage .gitignore, and generate Conventional Commit messages with explanations, protecting against committing sensitive files.

Core Features & Use Cases

  • Automatic .gitignore validation and updates for sensitive patterns
  • File classification into AUTO_EXCLUDE / AUTO_COMMIT / CONFIRM
  • Generate high-quality Conventional Commit messages with rationale

Quick Start

Say "commit" or "git commit" to start; Claude will propose a structured Conventional Commit message.

Frequently Asked Questions about git-commit-assistant

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

FAQPage Schema
How do I prevent accidentally committing sensitive files like credentials or API keys?▼

This Skill automatically identifies sensitive files during commit workflows by analyzing your repository and .gitignore patterns, then blocks credentials and secrets from being staged. It classifies files as AUTO_EXCLUDE, AUTO_COMMIT, or CONFIRM to guide safe decisions before you push.

What's the best way to write Conventional Commit messages for my Git workflow?▼

Conventional Commits follow a structured format (type: description) that standardizes your commit history. This Skill generates high-quality Conventional Commit messages with rationale based on your staged changes, improving readability and enabling automated changelog generation.

How can I update my .gitignore to catch sensitive patterns I'm missing?▼

.gitignore files define which files Git ignores; gaps leave secrets exposed. This Skill validates your .gitignore against staged changes, proposes updates for missing sensitive patterns, and helps you maintain coverage as your repository grows.

Can I automate file classification decisions during commit preparation?▼

Yes. This Skill analyzes git status and classifies each changed file automatically—marking obvious commits, excluding sensitive data, and prompting you only for ambiguous items. This reduces manual review while maintaining safety.

Why should I use Conventional Commits instead of freeform commit messages?▼

Conventional Commits enable machines to parse your history, automate versioning, and generate changelogs. They also make code review faster by signaling intent (fix, feature, breaking change) in the message structure itself.

Related Skills

Explore More Software Engineering Skills→
LirsakuraLirsakura
10

sync-log

Log Git push and pull operations to monthly Markdown files.

Community
Basic
linenoizelinenoize
1

git

Generate conventional git commits, branch names, and pull request descriptions.

Community
Advanced
mcj-codermcj-coder
1

branching-strategy-and-conventions

Configure Git branching strategies, Conventional Commits, and merge rules.

Community
Advanced
mattbobambrosemattbobambrose
1

check-secrets

Detect committed secrets and sensitive files in git history and working tree.

Community
Intermediate