commit

Stage Git changes and draft conventional commit messages while filtering secret files.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/marcelocantos/skills --skill commit-marcelocantos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/marcelocantos/skills/tree/main/skills/commit
Command: npx skills add https://github.com/marcelocantos/skills --skill commit-marcelocantos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often waste time manually staging files, crafting commit messages, and risk committing sensitive information. This Skill automates the entire commit workflow, safely handling secrets and producing well‑formed messages.

Core Features & Use Cases

  • Automated repo state gathering: Collects status, diffs, untracked files, and identifies potential secret files.
  • Intelligent filtering: Excludes secret‑candidate files and warns about possible credential leaks.
  • AI‑drafted commit messages: Generates concise, conventional‑style messages based on staged changes, with optional user‑provided text.
  • Amend and hook handling: Supports --amend and gracefully recovers from pre‑commit hook failures.

Quick Start

Invoke /commit to automatically stage changes and generate a concise commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commit messages and staging at the same time?

To automate git commit messages and staging, this skill analyzes repository diffs and untracked files, automatically stages changes, and drafts a conventional commit message. It runs a Bash script to gather repository state and filter out secret files before committing.

How can I prevent secret files and credentials from being committed to git?

To prevent secret files and credentials from being committed to git, this skill identifies potential secret candidates during the staging process and filters them out. It warns you about possible credential leaks to ensure safe commits without exposing sensitive information.

What is the best way to generate conventional commit messages from staged changes?

The best way to generate conventional commit messages from staged changes is using an automated drafting tool that analyzes diff statistics. This skill produces concise, conventional-style messages based on the actual repository changes, with support for optional user-provided text.

Does this automated commit skill handle pre-commit hook failures and amends?

Yes, this automated commit skill handles pre-commit hook failures by gracefully recovering from them. It also supports the --amend flag, allowing you to modify the most recent commit while maintaining the automated message drafting and secret filtering workflows.

Can I use this commit automation in any Git repository?

Yes, you can use this commit automation in any Git repository. It operates universally across repositories by running a Bash gathering script to collect status, diff statistics, and untracked files, ensuring safe commits regardless of the specific project context.