commit

Stage all Git changes, scan for secrets, and commit with conventional format.

3|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/giladresisi/ai-dev-env --skill commit-giladresisi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/giladresisi/ai-dev-env/tree/main/skills/commit
Command: npx skills add https://github.com/giladresisi/ai-dev-env --skill commit-giladresisi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all your code changes are saved to Git with meaningful commit messages, preventing data loss and maintaining a clear project history.

Core Features & Use Cases

  • Automated Staging: Stages all modified, added, and untracked files for commit.
  • Secret Scanning: Scans staged changes for potential secrets or credentials before committing.
  • Conventional Commits: Enforces a structured commit message format including type, scope, description, and a mandatory reason.
  • Use Case: After implementing a new feature, use this skill to automatically stage all your code, check for accidental secret commits, and create a well-formatted commit message explaining why the changes were made.

Quick Start

Use the commit skill to save your current changes to git.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I commit all uncommitted changes to git with a structured message?

To commit all uncommitted changes to git, this skill automatically stages all modified, added, and untracked files, then generates a structured conventional commit message with a mandatory detailed reason in the commit body to save your work.

How does secret scanning work before committing code to version control?

Secret scanning before committing code works by automatically analyzing staged changes for potential credentials or secrets, preventing accidental credential leaks and ensuring sensitive data is blocked from entering the git repository history.

What is the conventional commit format and why do I need a reason in the body?

The conventional commit format structures git messages with a type, scope, and description. You need a mandatory detailed reason in the commit body to enforce clear project history, preventing data loss and explaining exactly why code changes were made.

Can I automatically stage all modified and untracked files for a git commit?

Yes, you can automatically stage all modified, added, and untracked files for a git commit. This skill handles automated staging across the entire repository, ensuring no local changes are missed before running the secret scanning phase.

What is the best way to prevent accidental credential leaks in git commits?

The best way to prevent accidental credential leaks in git commits is to enforce a mandatory secret scanning phase on staged changes. This automated check scans for potential secrets or credentials before finalizing the commit, blocking sensitive data exposure.

Does this git commit tool work without manual staging or external dependencies?

Yes, this git commit tool works without manual staging by automatically adding all modified and untracked files. It operates with no external dependencies, handling staging, secret scanning, and conventional commit formatting autonomously.