Skip to content

JPeetz/agent-skills / skills/git-release/git-workflow-automation

git-workflow-automation

Verified

Use 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.

FileKindSize
CHANGELOG.mdmarkdown1.7 KB
LICENSEother12 B
SKILL.mdskill md8.4 KB
evals/evals.jsonconfig2.4 KB
references/conventional-commits-spec.mdmarkdown1.5 KB
references/keep-a-changelog-format.mdmarkdown2.0 KB
references/semver-cheatsheet.mdmarkdown1.4 KB
scripts/generate-changelog.shexecutablescript1.2 KB
scripts/next-version.shexecutablescript1.1 KB
scripts/validate-commits.shexecutablescript1003 B

references/keep-a-changelog-format.md

View on GitHub
# Keep a Changelog Format Reference

## Guiding Principles

- Changelogs are for humans, not machines
- There should be an entry for every single version
- The same types of changes should be grouped
- Versions and sections should be linkable
- The latest version comes first
- The release date of each version is displayed

## Standard Sections

```markdown
## [VERSION] — YYYY-MM-DD

### Added
for new features

### Changed
for changes in existing functionality

### Deprecated
for soon-to-be removed features

### Removed
for now removed features

### Fixed
for any bug fixes

### Security
in case of vulnerabilities
```

## How to Keep a Good Changelog

1. **Write for humans.** Don't just paste git log. Translate technical commit messages into user-facing language.
2. **One entry per version.** Don't stack multiple releases under one heading.
3. **Link to diffs.** `[1.2.0]: https://github.com/user/repo/compare/v1.1.0...v1.2.0`
4. **Don't list refactors, style changes, or internal-only changes.** Users don't care about renamed variables.
5. **Don't use "various bug fixes and improvements".** Be specific.
6. **Sort by importance.** Most impactful changes first in each section.
7. **Date format: YYYY-MM-DD.** ISO 8601, always.

## Example

```markdown
## [1.2.0] — 2024-06-15

### Added
- Dark mode support with system preference detection
- CSV export for all report types
- Bulk user import via admin panel

### Changed
- Dashboard loads 3x faster with server-side pagination
- Email notifications now use brand templates

### Fixed
- Login redirect loop when session expires mid-form
- Date picker showing wrong timezone for UTC+X users

### Security
- Rate limiting on login endpoint (5 attempts per minute)
- XSS sanitization on user-generated content
```

## Version Links (at bottom of file)

```markdown
[1.2.0]: https://github.com/user/repo/compare/v1.1.0...v1.2.0
[1.1.0]: https://github.com/user/repo/compare/v1.0.0...v1.1.0
[1.0.0]: https://github.com/user/repo/releases/tag/v1.0.0
```
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexUnverifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall