grepai: Skill for Claude Code

Release Process for grepai

This skill guides you through creating a new release. All output must be in English.

When to Use This Skill

Invoke this skill when:

• User asks to "create a release"
• User asks to "publish a new version"
• User asks to "bump the version"
• User mentions "release" in the context of versioning

Release Workflow

Step 1: Verify CI on Main

Check that all CI checks pass on main:

gh run list --branch main --limit 1 --json status,conclusion,name

STOP if CI is not green. Ask the user to fix issues first.

Step 2: Get Current Version and Changes

Get the latest release:

gh release list --limit 1

List merged PRs since last release:

gh pr list --state merged --base main --json number,title,author,mergedAt,labels --limit 50

Display a summary of changes categorized by type (feat, fix, docs, etc.).

Step 3: Determine Version Type

Change Type	Version Bump
Breaking changes	Major (vX+1.0.0)
New features (feat)	Minor (vX.Y+1.0)
Bug fixes (fix)	Patch (vX.Y.Z+1)
Docs/chore only	Usually no release needed

Ask user confirmation before proceeding.

Step 4: Update Version Files

4.1 CHANGELOG.md

Add new section after ## [Unreleased]:

## [X.Y.Z] - YYYY-MM-DD

### Added
- **Feature Name**: Description (#PR) - @author

### Fixed
- **Fix Name**: Description (#PR) - @author

Update comparison links at bottom:

[Unreleased]: https://github.com/yoanbernabeu/grepai/compare/vX.Y.Z...HEAD
[X.Y.Z]: https://github.com/yoanbernabeu/grepai/compare/vPREVIOUS...vX.Y.Z

4.2 Documentation Hero

Update version in docs/src/components/homepage/Hero.astro line 6:

const { version = "X.Y.Z" } = Astro.props;

4.3 Nix Flake

Update flake.nix:

1. Update version (line 13):

version = "X.Y.Z";

1. Update vendorHash:
   • Set vendorHash = ""; temporarily in flake.nix
   • Run make nix-hash to compute the correct hash (requires Docker)
   • Replace with the new hash: vendorHash = "sha256-XXXXX";
   • If Docker is not available, ask the user to provide the hash or skip this step