git

Automate Git commits, pushes, and branch management with Conventional Commits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nera0875/BUILDER --skill git-nera0875
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/nera0875/BUILDER/tree/main/.claude/skills/git
Command: npx skills add https://github.com/nera0875/BUILDER --skill git-nera0875

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This Skill streamlines Git workflow by automating commits, enforcing semantic commit messages, and managing GitHub interactions. It ensures a clean, traceable version history, reduces manual Git operations, and facilitates consistent project collaboration and releases.

Core Features & Use Cases

  • Automated Semantic Commits: Automatically stages and commits changes with Conventional Commit messages (feat, fix, refactor), including a "Generated with Claude Code" footer for traceability.
  • GitHub Integration: Handles repository initialization, remote setup, and pushing to GitHub, including creating releases with semantic versioning.
  • Branch Management: Supports both direct commits to main for rapid prototyping and feature branch workflows (create, push, merge, delete) for larger projects.
  • .gitignore Setup: Automatically creates a project-specific .gitignore file to prevent committing unnecessary files and maintain repository cleanliness.
  • Use Case: After completing a new feature, the AI will automatically commit the changes with a descriptive message like "feat(dashboard): add stats cards" and, if requested, push it to GitHub.

Quick Start

Commit all current changes with a message "feat(auth): implement user login form" and push to the 'main' branch on GitHub.

Frequently Asked Questions about git

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

FAQPage Schema
How do I automate Git commits with semantic messages?

Automated semantic commits enforce Conventional Commits format (`feat`, `fix`, `refactor`) with descriptive messages and a traceability footer. This Skill stages changes and commits them automatically after feature completion, reducing manual Git operations and maintaining a clean, traceable version history.

Can I push commits to GitHub automatically after completing a feature?

Yes. This Skill integrates with GitHub to automatically push commits after semantic messaging, handle repository initialization, and create releases with semantic versioning. It streamlines the workflow from local changes through remote repository updates.

What's the best way to manage feature branches and merges in automated workflows?

This Skill supports both direct commits to `main` for rapid iteration and feature branch workflows for larger projects, including branch creation, pushing, merging, and deletion. Choose the approach that matches your project scale and collaboration needs.

How does this Skill prevent committing unnecessary files?

It automatically generates a project-specific `.gitignore` file during setup, preventing unnecessary files from entering the repository and maintaining cleanliness. This ensures only relevant code and assets are tracked.

Does this Skill work with backend and frontend codebases?

Yes. It applies to both backend and frontend codebases, supporting feature and bugfix cycles across the full stack. Workflow automation activates after feature completion or keyword triggers in either codebase type.

Do I need GitHub CLI (`gh`) to use this Skill?

Yes. GitHub CLI (`gh`) is a required dependency for GitHub integration, including repository operations, push actions, and release management. Ensure it is installed and authenticated before use.