JPeetz/agent-skills / skills/git-release/git-workflow-automation
git-workflow-automation
VerifiedUse this skill when automating Git workflows — commit message generation, branch naming, PR description writing, changelog generation, merge conflict resolution, and release management. Activates when users say "write a commit message", "create a PR", "generate changelog", "branch name for", "resolve merge conflict", "cut a release", "bump version", "semantic version", or "conventional commits". Enforces Conventional Commits, semantic versioning, and reproducible Git workflows across teams.
| File | Kind | Size |
|---|---|---|
| CHANGELOG.md | markdown | 1.7 KB |
| LICENSE | other | 12 B |
| SKILL.md | skill md | 8.4 KB |
| evals/evals.json | config | 2.4 KB |
| references/conventional-commits-spec.md | markdown | 1.5 KB |
| references/keep-a-changelog-format.md | markdown | 2.0 KB |
| references/semver-cheatsheet.md | markdown | 1.4 KB |
| scripts/generate-changelog.shexecutable | script | 1.2 KB |
| scripts/next-version.shexecutable | script | 1.1 KB |
| scripts/validate-commits.shexecutable | script | 1003 B |
references/conventional-commits-spec.md
View on GitHub# Conventional Commits Specification Reference
## Summary
The Conventional Commits specification is a lightweight convention on top of commit messages.
It provides an easy set of rules for creating an explicit commit history;
which makes it easier to write automated tools on top of.
## Specification
Commits MUST be prefixed with a type noun (feat, fix, etc.)
An optional scope MAY be added after type, enclosed in parentheses.
A colon and space MUST follow type (and optional scope).
A description MUST immediately follow the colon and space.
```
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
```
## Why Use Conventional Commits
- Automatically generating CHANGELOGs
- Automatically determining a semantic version bump
- Communicating the nature of changes to teammates, the public, and other stakeholders
- Triggering build and publish processes
- Making it easier for people to contribute to your projects
## FAQ
### How do I indicate a breaking change?
Add `!` before the colon, OR add `BREAKING CHANGE:` footer.
- `feat!: remove deprecated API`
- `feat(api)!: change user response format`
- Footer: `BREAKING CHANGE: The user response no longer includes the 'meta' field`
### What types are standard?
feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
### Are types case-sensitive?
Yes. Always lowercase. `Feat` and `FEAT` are not valid.
### What about merge commits?
Merge commits (both GitHub PR merges and `git merge`) do not need to follow this format.
However, the commits being merged SHOULD be conventional.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |