skills.rest
ivanrvpereira
ivanrvpereiraCOMMUNITY
Explore all skills by this author →
𝕏@ivanrvpereiraGitHub

git-commit

Create atomic Git commits with repo-aligned messages and secret safety checks.

17|Updated Feb 19, 2026
Search Tags:#git#code review#version control#commit message#safety checks#repository hygiene#atomic changes
One-click install
npx skills add https://github.com/ivanrvpereira/.agents --skill git-commit-ivanrvpereira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/ivanrvpereira/.agents/tree/main/skills/git-commit
Command: npx skills add https://github.com/ivanrvpereira/.agents --skill git-commit-ivanrvpereira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you produce a tidy Git history by guiding you to create small, focused, review-friendly commits with clear and consistent messages.

Core Features & Use Cases

  • Phase 1: Change review & safe staging: Checks for changes, stages only what’s appropriate, and avoids committing files that look like secrets (e.g., .env, credentials, API keys).
  • Phase 2: Commit message generation with repo style: Produces a subject line that follows common conventions, adds an optional body focused on why, and aligns tone/structure with recent commits.
  • Phase 3: Safe commit execution: Commits without forcing bypasses, avoids amending unless requested, and discourages unsafe remote pushes.

Quick Start

Ask the agent to create a clean, atomic Git commit by reviewing current changes, staging appropriately, drafting a repo-style message, and running git commit.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I create small atomic Git commits with clear messages?▼

To create atomic Git commits, review working-directory changes, stage only related modifications, and generate a message with an imperative subject and an optional body explaining the rationale. This prevents mixed commits and keeps the history reviewable.

How can I prevent committing secrets and credentials to my Git repository?▼

Prevent committing secrets by applying safety checks to identify and avoid staging files that resemble credentials, such as .env files or API keys. This ensures sensitive data remains excluded from the repository history.

What is the best way to format Git commit messages for code review?▼

The best way to format Git commit messages for code review is using an imperative subject line and an optional wrapped body focused on why the change was made. Aligning tone and structure with recent commits maintains consistency.

How do I split mixed working-directory changes into focused Git commits?▼

Split mixed changes by checking staged and unstaged differences, selectively staging only appropriate related modifications, and committing them individually. This workflow transforms unclear edits into small, focused commits with clear rationale.

Can I amend commits or force push changes safely in local development?▼

You can amend commits only if explicitly requested, but the workflow discourages unsafe remote pushes and avoids forcing bypasses. This approach prioritizes safe commit execution without altering remote history unexpectedly.

Related Skills

Explore More Software Engineering Skills→
mkittmkitt
6

commit-groups

Analyze uncommitted Git changes to propose logical commit groupings.

Community
Intermediate
lips85lips85

git-pushing

Stage all changes, create a conventional commit, and push to the remote repository.

Community
Basic
gebrudergebruder
166

git

Automate Git version control commands for repository operations.

Community
Intermediate
imMamdouhaboammarimMamdouhaboammar

commit-work

Stage and commit changes with Conventional Commits format.

Community
Intermediate