auto-commit

Convert git status outputs into atomic commits with linting and secret scanning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the repeatable git commit workflow by turning git status outputs into atomic commits, applying linting, scanning for secrets, and handling bootstrap for new repos.

Core Features & Use Cases

  • Atomic commits derived from git status across worktrees.
  • Linting and secret scanning integrated into the commit flow.
  • Push via GitHub CLI with optional remote bootstrap for brand-new repos (git init, gh repo create).
  • Supports bootstrap and safe defaults for new repositories to publish changes efficiently.

Quick Start

Start the workflow from the repository root by running the auto-commit process after a git status check.

Frequently Asked Questions about auto-commit

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

FAQPage Schema
How do I automate atomic git commits from my staged changes?

Atomic git commits are generated by parsing git status outputs to group related changes into isolated commits. The workflow applies linting, executes secret scanning, and enforces standardized commit messages under 72 characters before pushing safely via GitHub CLI.

Can I use gh cli to bootstrap and push a brand-new git repository?

Yes, you can bootstrap a brand-new git repository by running git init and using gh cli to create the remote repository. This workflow provides safe defaults to automatically publish your initial changes efficiently without manual remote setup.

How does secret scanning integrate into the git commit workflow?

Secret scanning integrates into the git commit workflow by automatically evaluating staged files for sensitive data before finalizing the commit. This prevents accidental exposure of credentials by halting the commit process when secrets are detected.

Do I need git worktrees to manage atomic commits across multiple features?

Git worktrees are supported to manage atomic commits across multiple feature branches simultaneously. This allows you to apply linting, secret scanning, and standardized commit message generation to isolated working directories without interfering with your main branch.

What is the best way to enforce standardized git commit messages under 72 characters?

The best way to enforce standardized git commit messages under 72 characters is by automating the commit generation process. This workflow parses git status to create atomic commits and strictly formats the resulting messages to meet the 72-character limit.