skills.rest
juanibiapina
juanibiapinaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit

Create Git commits only after explicit user confirmation and safety checks.

30|5|Updated Aug 9, 2012
Search Tags:#git#workflow#commit#safety#developer-tools#guardrails
One-click install
npx skills add https://github.com/juanibiapina/dotfiles --skill git-commit-juanibiapina
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/juanibiapina/dotfiles/tree/main/dotfiles/agents/.agents/skills/git-commit
Command: npx skills add https://github.com/juanibiapina/dotfiles --skill git-commit-juanibiapina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Only create commits when requested by the user. If unclear, ask first. This workflow provides safety guidelines to avoid destructive actions and ensures commits reflect explicit user intent.

Core Features & Use Cases

  • Explicit prompts: Commits only happen after user confirmation.
  • Safety protocol: Enforces checks on hooks, prevents dangerous commands, and prevents accidental pushes.
  • Guided workflow: Includes rules for amend, no-verify, and push cautions; suitable for collaborative review and feature-branch workflows.

Quick Start

Ask to create a new git commit and specify the exact changes and any desired hooks or options.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I prevent accidental git commits and unintended pushes?▼

To prevent accidental git commits, this workflow enforces explicit user confirmation before creating any commit and applies guardrails against unintended pushes, ensuring changes reflect your explicit intent.

What's the best way to manage git commit safety on collaborative feature branches?▼

Managing git commit safety on collaborative branches requires checks on amend operations and hook usage; this workflow provides guided rules to prevent dangerous commands and careless hook application.

When should I use git amend and no-verify hooks during a commit?▼

You should use git amend and no-verify hooks cautiously; this workflow defines specific guardrails around these actions, requiring explicit user requests and providing cautions to prevent unintended changes.

Can I create on-demand git commits without triggering automated hooks?▼

Yes, you can create on-demand git commits while controlling hook behavior, as this workflow includes a safety protocol that enforces checks on hook usage and prevents accidental execution of dangerous commands.

Why does my git workflow need explicit prompts before committing changes?▼

Your git workflow needs explicit prompts to ensure commits reflect user intent and avoid destructive actions, guarding against scenarios where accidental commits or careless hook usage cause issues.

Related Skills

Explore More Software Engineering Skills→
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
guille-galloguille-gallo

setup-pre-commit

Automate pre-commit hook setup with Husky and lint-staged for Git repositories.

Community
Intermediate
ownway22ownway22

git-commit

GenerateCommitmentlesslyOptimizedAutomatedlyTypedAndStyledCommit messages with intelligent detection of commit type and scope.

Community
Advanced