git-commit_skill

This skill guides a safe, conventional-commits based git workflow, automatically staging changes, crafting messages, and optionally pushing.
  • Python

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill yousufjoyian/claude-skills --skill git-commit

  • SKILL.md11.3 KB

Overview

This skill provides a smart, safe git commit workflow that stages changes, crafts conventional commit messages, and performs optional pushes. It inspects the working tree, prevents committing secrets or dangerous operations, and adds co-author attribution automatically. The workflow is designed to be predictable and auditable for local development or CI-assisted commits.

How this skill works

It analyzes the repository state (unstaged, staged, untracked files) and shows a concise diff summary before any actions. It performs smart staging while excluding common secret patterns, generates Conventional Commits-style messages with optional body and Co-Authored-By attribution, and runs safety checks to avoid risky commands. If requested, it pushes to origin and produces a visual push summary.

When to use it

  • Commit local changes with a clear, conventional commit message
  • Commit a selected subset of files instead of everything
  • Commit + push in one step when ready to publish to origin
  • When you want automatic co-author attribution added
  • When you need safety checks to prevent committing secrets or forcing pushed history

Best practices

  • Review the diff summary before staging or committing
  • Never force-push without explicit confirmation
  • Exclude common secret patterns (.env, *.key, credentials.json) from staging
  • Use Conventional Commits format: type(scope): short description, with optional body
  • Respect pre-commit hooks; fix issues rather than bypassing with --no-verify

Example use cases

  • User says “commit”: show status, stage safe files, craft a conventional commit, and commit locally
  • User says “commit these files”: stage listed files (excluding secrets) and commit with a tailored message
  • User says “commit and push”: perform commit then push to origin and return a visual push summary
  • Handle pre-commit failures by reporting hook output and guiding fixes rather than forcing a commit
  • Amend last commit only when explicitly requested and safe (not pushed and created this session)

FAQ

The skill warns and stops staging that file, instructing you to remove it from staging with git reset HEAD <file> before committing.

Can this skill amend the last commit?

Yes, but only when you explicitly request amend and the last commit was created in the same session and has not been pushed.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational