git-operator_skill

Overview

This skill manages Git operations with project-specific conventions and best practices. It drafts and creates commits that are logically grouped, formatted according to configured commit message rules, and respects push and signature policies. The skill reads configuration from a .claude/config.yaml file to adapt language, signature, and push behavior.

How this skill works

Before any commit, the skill inspects git status, diffs, and recent log history to understand changes and the repository's style. It groups files by purpose, drafts conventional commit messages focused on role/purpose, stages the appropriate files, creates atomic commits, and conditionally executes git push based on configuration. When enabled, it appends a conditional Claude Code signature according to policy.

When to use it

• After completing a feature implementation or bug fix
• When you need commits that follow project conventions and are atomic
• Before switching branches or finishing a development milestone
• When automated agents or CI pipelines must create standardized commits
• When you want commits drafted in the repository's configured language

Best practices

• Read .claude/config.yaml first to get output.language, git.claude_signature, and git.allow_push
• Run git status and git diff to confirm the full scope of changes before committing
• Group related edits into a single commit and separate different concerns
• Follow conventional commit format: <type>: <subject> and keep messages role-focused
• Ensure commits are atomic: build and tests should pass after each commit
• Only push automatically if git.allow_push is explicitly true

Example use cases

• Add a new feature with tests combined into a single feat: commit
• Split two unrelated bug fixes into separate fix: commits for clear history
• Refactor shared logic across multiple files and commit as a single refactor: change
• Create documentation-only changes using docs: with no code changes
• Run from an orchestrator agent to commit validated deliverables respecting push policy