Agent-Skills.md

Agent Skills: Git Operator

Rules and procedures for Git operations (add, branch, commit, push). Use when performing git add, git commit, git push, or creating branches.

UncategorizedID: scizorman/dotfiles/git-operator

Repository

scizorman/dotfiles
scizormanLicense: MIT
1

Install this agent skill to your local

pnpm dlx add-skill https://github.com/scizorman/dotfiles/tree/HEAD/modules/home/coding-agent/config/skills/git-operator

Skill Files

Browse the full folder contents for git-operator.

Download Skill

Loading file tree…

modules/home/coding-agent/config/skills/git-operator/SKILL.md

Skill Metadata

Name
git-operator
Description
Rules and procedures for Git operations (add, branch, commit, push). Use when performing git add, git commit, git push, or creating branches.

Git Operator

This skill defines procedures for Git operations.

Staging

Stage only task-related files. Do not use git add . or git add -A without explicit confirmation.

git status                  # Run this first
git add <file>              # Stage specific files

Before staging, verify:

  • No secrets (.env, credentials.json, API keys)
  • No unrelated changes included

Branch Creation

Branch names must be in kebab-case.

Good: add-user-authentication, fix-login-bug, update-readme Bad: addUserAuthentication, Add_User_Auth, ADD-USER-AUTH

git switch -c <branch-name>

Commit

Follow Conventional Commits format.

<type>(<scope>): <description>

[optional body]

Types

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code
  • refactor: Code changes that neither fix a bug nor add a feature
  • perf: Code changes that improve performance
  • test: Adding or modifying tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files or scripts
  • chore: Other changes (not modifying src or test)

Procedure

Analyse staged changes to create a message focusing on "why" rather than "what".

git diff --cached           # Review staged changes
git commit -m "<type>(<scope>): <description>"

Good example:

fix(auth): prevent session timeout on mobile

Users reported being logged out after 5 minutes on mobile.
Root cause was incorrect token refresh interval.

Bad example:

fixed bug

For multi-line messages, use HEREDOC:

git commit -m "$(cat <<'EOF'
<type>(<scope>): <description>

<body>
EOF
)"

Push

Pre-push Verification

Run these commands before pushing:

git log --oneline -5        # Verify recent commits
git branch -vv              # Verify current branch and tracking
git status                  # Ensure working directory is clean

Proceed only after reviewing the output.

Procedure

For new branches:

git push -u origin <branch-name>

For existing remote tracking branches:

git push