Git Release Automation

## Overview

Git Release Automation streamlines your version release pipeline: write standardized commits, auto-generate changelogs, and publish GitHub Releases — all through a repeatable workflow. Best suited for teams that already have a Git/GitHub setup and want to eliminate manual release toil.

## Quick Start

1. Install the plugin: `npx skillstore plugin install git-release-automation`
2. Use the **commit** skill to create conventional commit messages with emoji prefixes when committing changes
3. Run **changelog-automation** to generate a Keep a Changelog formatted log from your recent commits and PRs
4. When ready to ship, use the **release** skill to create git tags, detect version bumps, and publish a GitHub Release

## Key Commands

- **commit** — Create well-formatted git commits following conventional commit conventions (feat, fix, chore, etc.) with emoji support. Analyzes your staged changes and generates descriptive commit messages automatically.
- **changelog-automation** — Generate changelogs from commits, PRs, and releases in Keep a Changelog format. Supports setting up automated release note workflows and standardizing commit conventions across your team.
- **release** — Automate the full version release workflow: git tag creation, version bump detection, and GitHub Release generation. Handles prefixed tagging for monorepo setups with multiple plugins in a single repository.

## Intended Audience

This plugin is for teams that already have an established Git/GitHub workflow and want to automate the commit → changelog → release pipeline. It does **not** set up repositories from scratch.

## Failure Handling

If a tag or release step fails, the workflow stops at the changelog stage — it will not automatically push a broken version. You can review the generated changelog, fix the issue, and re-run the release step.

## Tips

- Pair with `github-pr-workflow` for end-to-end coverage: PRs + reviews (that plugin) → commits + releases (this plugin)
- Use **commit** as your daily driver to build clean commit history, then **changelog-automation** before each release
- For monorepos, the **release** skill handles prefixed tags (e.g., `@my-plugin/v1.2.0`) automatically