git-manager

Automate Git commits with identity setup and pre-commit checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, manual, and often error-prone process of managing Git commits. It streamlines your workflow, ensures best practices, and prevents accidental exposure of sensitive data, allowing you to focus purely on your code.

Core Features & Use Cases

  • Automated Git Identity: Configures your Git user name and email, either by detecting from your environment (e.g., SSH keys), loading from .env, or interactively prompting you, then persists it for future use.
  • Interactive Commit Workflow: Guides you step-by-step through selecting a branch, reviewing changes, crafting a conventional commit message, and confirming the push to your remote repository.
  • Sensitive File Protection: Automatically scans for and warns about sensitive files (like .env, .pem, credentials) before staging, giving you the option to exclude them and prevent accidental leaks.
  • Conventional Commit Support: Assists in generating structured commit messages (e.g., feat:, fix:, docs:) to maintain a clean and understandable commit history.
  • Push Confirmation: Requires explicit user confirmation before pushing changes to the remote, safeguarding against unintended updates to shared branches.

Quick Start

Use the git-manager skill to commit all my changes.

Frequently Asked Questions about git-manager

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

FAQPage Schema
How do I automate Git commits and prevent accidental pushes of sensitive files?

Automate Git commits by scanning for sensitive files like `.env` and `.pem` before staging, then generating conventional commit messages with user confirmation before pushing. This prevents accidental exposure of credentials while maintaining a clean commit history.

Can I automatically configure my Git identity from environment variables or SSH keys?

Git identity can be automatically detected from your environment (SSH keys, `.env` files) or set interactively, then persisted for future commits. This eliminates manual configuration and ensures consistent authorship across your repository.

What's the best way to enforce conventional commit messages in my workflow?

Enforce conventional commits by using structured message generation that guides you through selecting commit type (`feat`, `fix`, `docs`), scope, and description, ensuring a clean and queryable commit history across your team.

How do I review changes and confirm commits before they reach the remote repository?

Review staged changes interactively, craft your commit message, and explicitly confirm the push to your remote branch. This workflow prevents unintended updates to shared branches and gives you full visibility before publishing.

Can Git commit automation handle branch selection and push orchestration?

Automate branch selection, staging, conventional message generation, and optional push orchestration through Python automation scripts invoked via uv, streamlining the entire commit workflow from code changes to remote synchronization.

What happens if sensitive files are detected during a Git commit?

When sensitive files are detected, you receive a warning listing them (like credentials or private keys) and get the option to exclude them from staging before the commit proceeds, preventing accidental credential leaks.