git

Automate safe Git workflows with status and diff checks before commits.

Updated Aug 12, 2018
One-click install
npx skills add https://github.com/ivanov-i/dots --skill git-ivanov-i
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/ivanov-i/dots/tree/main/codex/skills/git
Command: npx skills add https://github.com/ivanov-i/dots --skill git-ivanov-i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers to perform Git operations safely and consistently, reducing the risk of destructive actions and messy commits.

Core Features & Use Cases

  • Safe by default: checks git status/diff/log before actions to avoid surprises.
  • Consistent commit practice: follow repo style; infer ticket numbers from branch when not explicit.
  • Guardrails for destructive operations: explicit permission required for resets, cleanups, or deletes.

Quick Start

Ask me to perform a safe, commit-ready operation on the current branch by checking status, reviewing diffs, and applying the repository's commit guidelines.

Frequently Asked Questions about git

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

FAQPage Schema
How do I prevent destructive Git actions when committing changes?

To prevent destructive Git actions, you can enforce guardrails that require explicit permission before executing resets, cleanups, or deletes. This approach checks git status, diff, and log beforehand to avoid surprising data loss.

What's the best way to create safe and consistent Git commits?

The best way to create consistent Git commits is to check repository status and diffs before staging, follow existing repo styles, and infer ticket numbers from the branch name. This promotes small, reviewable commits.

How does a safe Git workflow handle branch naming and ticket numbers?

A safe Git workflow handles ticket numbers by automatically inferring them from the current branch name when they are not explicitly provided. This ensures commits are consistently linked to tracking issues.

Do I need to review diffs before pushing code in a safe Git workflow?

Yes, reviewing diffs is required in a safe Git workflow. Checking git status and diffs before performing edits or pushing code is a core constraint that prevents unexpected conflicts and messy commit histories.

Can I automate Git code review and branching guardrails?

Yes, you can automate Git code review and branching guardrails to apply safety constraints across typical development scenarios. This enforces explicit permissions for destructive operations and ensures small, reviewable commits.