git-workflow

Invoke before any git operations — branching, committing, merging, or creating pull requests. Contains project-specific branch naming, commit format, and merge strategy.

Type · Core skillRules · 3Template · .claude/skills/git-workflow/SKILL.mdView on GitHub ↗

The SKILL.md template

Core skill — installs for every project. Your edits to Rules, Gotchas, and Examples are preserved across re-initialization.

markdown

# Git Workflow

## Detected
<!-- Populated by scan during init. Do not edit manually. -->

## Rules
- Commit each logical change separately. Don't batch unrelated changes into one commit.
- Write commit messages that explain what changed and why: `feat: add input validation to signup` not `update files`.
- Stage specific files for each commit. Avoid `git add .` or `git add -A` — review what you're committing.

## Gotchas
*Not yet captured. Add as you discover them during development.*

## Examples
*Not yet captured. Add short snippets showing the RIGHT way.*

View on GitHub ↗

Note

This is the template that ships with ana init. Your project’s version will have the Detected section populated by scan and may have additional rules promoted from findings.