commit

Collect uncommitted Git changes and create a conventional commit message.

138|5|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/termide/termide --skill commit-termide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/termide/termide/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/termide/termide --skill commit-termide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid manual, error-prone commit messaging by collecting all uncommitted changes and producing a single, semantically meaningful commit that documents intent clearly.

Core Features & Use Cases

  • Semantic commits: Generate conventional commits that describe the change scope and purpose.
  • Selective staging: Exclude sensitive files (e.g., secrets or credentials) from commits.
  • Context-aware messaging: Analyze git status, diffs, and recent history to determine the appropriate scope and message.

Quick Start

Run the skill to collect all uncommitted changes and create a single conventional commit.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commit messages for multiple uncommitted files?

Automate conventional commits by collecting uncommitted changes and analyzing git diffs and history to produce a single semantic message. The tool selectively stages files, excluding secrets, and applies structured conventional-commits formatting.

Can I exclude sensitive files like credentials from automated git staging?

Yes, automated git staging can exclude sensitive files and credentials. The skill analyzes repository status and selectively stages files, ensuring that secrets are not included in the final conventional commit.

How do conventional commits determine the scope and intent of my git changes?

Conventional commits determine scope and intent by analyzing git status, diffs, and recent history. This context-aware mechanism evaluates uncommitted changes across multiple files to generate a semantically meaningful message.

What is the best way to group multiple file changes into a single semantic commit?

The best way to group changes into a semantic commit is analyzing all uncommitted files together. This skill evaluates git diffs and recent history to determine the shared scope and intent, creating one structured conventional commit.

Do I need a specific git workflow to generate semantic commit messages automatically?

You need an existing Git repository with uncommitted changes to generate semantic commit messages automatically. The skill operates within standard version-control workflows by analyzing current diffs and recent commit history.

Why does automated commit generation analyze recent git history?

Automated commit generation analyzes recent git history to determine the appropriate scope and intent for new changes. Reviewing past conventional commits ensures the new semantic message aligns with the existing project context.