git

Standardizes Git status review, diff inspection, and Conventional Commits for repository changes.

Updated Sep 20, 2026
One-click install
npx skills add https://github.com/aascer39/codeagent --skill git-aascer39
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/aascer39/codeagent/tree/main/.agents/skills/git
Command: npx skills add https://github.com/aascer39/codeagent --skill git-aascer39

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents messy commit histories, unverified code submissions, accidental commits of secrets or build artifacts, and lost records of human corrections when AI and humans collaborate on the same repository. ## Core Features & Use Cases - Commit Protocol: Enforces Conventional Commits with stage or Issue references, structured bodies (What changed / Why / Human Corrections / Verification), and type selection rules for feat, fix, refactor, test, docs, perf, style, and chore. - Pre-Commit Verification Workflow: Defines an ordered checklist covering git status, scoped diffs, staged diff review, risk-based validation commands, and post-commit cleanliness checks. - Human-AI Collaboration Rules: Requires recording human corrections in commit bodies, re-verifying after manual edits, and forbids overwriting unknown working-tree changes with reset or restore. - Use Case: After an AI implements a shell execution tool and a human adjusts the timeout, the Skill produces a commit like "feat: V1-03 implement shell command execution tool" with a body documenting the AI changes, the human correction, and the actual test command results. ## Quick Start Review the current working tree changes and create a properly formatted commit following the git commit protocol.

Frequently Asked Questions about git

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

FAQPage Schema
How do I write a good commit message for AI-generated code?▼

Use the format "<type>: <stage or Issue> <summary>" with a body containing What changed, Why, Human Corrections, and Verification sections. The summary must describe the actual object and behavior changed, matching the real diff.

What should I check before running git commit?▼

Run git status --short, scoped git diff, and git diff --cached to confirm only task-related files are staged. Verify no secrets, build artifacts, or temporary files are included, execute relevant validation commands, then commit and confirm a clean working tree.

Which Conventional Commits type should I use for a bug fix with tests?▼

Use "fix:" when the primary purpose is fixing a bug, even if tests were added; record the new tests in the commit body. Choose the type by main intent: feat for new features, fix for bugs, refactor for behavior-preserving restructuring.

Can AI tools run git reset --hard on uncommitted changes?▼

No. The protocol forbids git reset --hard, git checkout ., and git restore . on unknown working-tree modifications. AI must inspect diffs, identify human edits, preserve them, and record human corrections in the commit body.

What files must never be committed to a repository?▼

Never commit .env files, API keys, tokens, passwords, or other secrets, plus build outputs like target/, node_modules/, *.class, and *.log files. Check git status before staging to catch these accidentally included files.