smart-commit

Automates git commits by grouping semantically related file changes into conventional format messages.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/djimontyp/task-tracker --skill smart-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-commit
Source: https://github.com/djimontyp/task-tracker/tree/main/.claude/skills/smart-commit
Command: npx skills add https://github.com/djimontyp/task-tracker --skill smart-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill intelligently analyzes your Git changes, groups semantically related modifications, and generates atomic commits with conventional commit messages, saving you time and ensuring a clean, reviewable Git history.

Core Features & Use Cases

  • Semantic Grouping: Automatically groups related file changes (e.g., tests with their implementation, shared symbols) into logical, atomic commits.
  • Conventional Commit Format: Generates commit messages following type(scope): description (e.g., feat(backend): add user authentication) for clear history.
  • Security Check: Flags sensitive files (e.g., .env, private keys) to prevent accidental commits.
  • Use Case: After making several changes across your backend, frontend, and tests, simply ask to "commit changes." This skill will create separate, well-structured commits for each logical change, making your pull requests easier to review and saving you manual effort.

Quick Start

To commit all changes automatically:

git status

... make changes ...

Then, in your AI assistant:

commit changes

To commit with review:

commit changes, ask me first

Frequently Asked Questions about smart-commit

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

FAQPage Schema
How do I automatically create semantic Git commits from multiple file changes?

Semantic Git commits group logically related changes into atomic, independently reviewable units. This Skill analyzes your code diffs, identifies relationships between files (shared symbols, test-implementation pairs, directory areas), and generates conventional commits with type and scope labels automatically, eliminating manual grouping.

What is a conventional commit format and why should I use it?

Conventional commits follow `type(scope): description` syntax (e.g., `feat(auth): add login flow`), making Git history scannable and enabling automated changelog generation. This Skill applies the format automatically to keep your version control clean and your pull requests easier to review.

Can this Skill prevent me from accidentally committing sensitive files?

Yes. This Skill flags sensitive files like `.env` and private keys before committing, blocking accidental exposure. You review flagged files and decide whether to exclude them, ensuring security compliance in your Git history.

How does the Skill group related file changes into separate commits?

The Skill reads your Git diff in parallel, extracts symbols and dependencies, and enforces grouping rules: tests stay with their implementations, shared symbols stay together, and directory-based changes stay atomic. Each group becomes one clean, conventional commit.

Do I need to review commits before they're created?

No by default, but you can request review first. Use `commit changes` for automatic commits or `commit changes, ask me first` to preview and approve each commit group before it's created.

What Git repositories or project structures does this work with?

This Skill works with any repository that has multi-file diffs and conventional commit support. It's designed for monorepos, multi-service projects, and standard Git workflows where atomic commits and clean history matter for code review and maintenance.