BA-CalderonMorales

release-checklist

@BA-CalderonMorales/release-checklist
BA-CalderonMorales
114
17 forks
Updated 1/18/2026
View on GitHub

Skill: Release Checklist: **Name**: release-checklist

Installation

$skills install @BA-CalderonMorales/release-checklist
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Path.github/skills/release-checklist/SKILL.md
Branchmain
Scoped Name@BA-CalderonMorales/release-checklist

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

skills list

Skill Instructions

Skill: Release Checklist

Name: release-checklist Description: Pre-release automation and checklist for hardening versions before tagging Trigger: "Before tagging", "Harden release", "Pre-release checklist", "Make this tag official"


Pre-Release Checklist

Execute these steps in order before making any version tag official:

1. CI/CD Verification

# Check all CI jobs are green
gh run list --limit 1 --json conclusion,status

# View specific run details
gh run view <run-id> --json jobs --jq '.jobs[] | "\(.name): \(.conclusion // .status)"'

Required: All jobs must show success

2. Version Synchronization

# Verify versions match across all distribution packages
grep '^version' Cargo.toml | head -1
grep '"version"' npm/terminal-jarvis/package.json | head -1
grep 'version "' homebrew/Formula/terminal-jarvis.rb | head -1

Required: All three must show identical version numbers

3. CHANGELOG Update

Ensure CHANGELOG.md contains:

  • Correct version number and date
  • All commits since last tag documented
  • Sections: Added, Changed, Fixed, Technical (as applicable)
# List commits since last tag
git log --oneline $(git describe --tags --abbrev=0)..HEAD

4. README Synchronization

# Sync main README to npm package
cp README.md npm/terminal-jarvis/README.md

5. Documentation Accuracy

Verify these README sections are current:

  • Project Structure module counts match actual src/ directories
  • Feature descriptions reflect current functionality
  • WIP features have appropriate disclaimers
  • Remote dev environment links are valid

6. Quality Gates

# Run full verification
./scripts/verify/verify-change.sh

# Or quick mode if tests already passed in CI
./scripts/verify/verify-change.sh --quick

7. Final Commit

git add -A
git commit -m "docs: prepare release vX.X.X"
git push

8. Wait for CI

# Monitor CI run
gh run watch

Automated Pre-Release Script

For AI agents, execute this sequence:

# 1. Check CI status
gh run list --limit 1 --json conclusion --jq '.[0].conclusion'

# 2. Version check
echo "Cargo: $(grep '^version' Cargo.toml | head -1)"
echo "NPM: $(grep '"version"' npm/terminal-jarvis/package.json | head -1)"

# 3. Sync README
cp README.md npm/terminal-jarvis/README.md

# 4. Quick verify
./scripts/verify/verify-change.sh --quick

# 5. Commit if all pass
git add -A && git commit -m "docs: prepare release vX.X.X" && git push

Post-Release Checklist

After tagging, verify distribution:

ChannelVerification Command
NPMnpm view terminal-jarvis version
Cargocargo search terminal-jarvis
Homebrewbrew info terminal-jarvis
GitHubgh release view vX.X.X

Common Issues

IssueDetectionResolution
CI still runninggh run list shows in_progressWait for completion
Version mismatchgrep shows different versions./scripts/cicd/local-cd.sh --update-version X.X.X
README out of syncdiff shows changescp README.md npm/terminal-jarvis/README.md
CHANGELOG missing entriesgit log shows unlogged commitsUpdate CHANGELOG.md manually
Module counts wrongls shows different file countsUpdate README Project Structure

Integration with Other Skills

  • verification: Run quality gates before release
  • versioning: Update version numbers across packages
  • deployment: Execute actual tagging and release
  • homebrew: Generate and publish Homebrew archives
  • npm: Publish to NPM registry