Skip to main content
command CX Codex

setup-automated-releases — Claude Code command: releases

setup-automated-releases sets up automated releases with versioning, conventional commits, GitHub Actions, changelogs, and pull request checks for a repository.

MIT 347 installs updated 2026-10-24

Install into Claude Code · claude-code-templates All methods and platforms ↓
npx claude-code-templates@latest --command deployment/setup-automated-releases
Open on GitHub

What setup-automated-releases does

The command inspects the project layout, current version, git tags, recent commit patterns, and existing workflows. It detects common project types and chooses a version location such as package.json, __init__.py, pyproject.toml, go.mod, or version.txt. The target format is MAJOR.MINOR.PATCH.

It then creates contribution rules, a pull request template, and workflows for release and PR validation. The release workflow can update the version, build release notes, edit CHANGELOG.md, create a git tag, publish a GitHub Release, and attach distribution artifacts. Release-note categories, Dependabot settings, and branch-protection guidance are included as well.

The release workflow targets GitHub Actions and runs after a push to main; a manual trigger is included for forced releases. Options also cover monorepos, libraries, and applications, with related versioning, API, Docker, or deployment settings.

What it helps with

  • set up semantic versioning for a repository
  • create GitHub Actions release workflows
  • validate pull request titles and commit messages
  • maintain a Keep a Changelog file
  • publish tagged GitHub Releases with artifacts

Example prompts for the agent

  • Run /deployment:setup-automated-releases --full-automation to configure the complete release setup.
  • Inspect the repository and configure semantic versioning with /deployment:setup-automated-releases --semantic.
  • Create the release workflow with /deployment:setup-automated-releases --github-actions.

How to install setup-automated-releases

1claude-code-templates

npx claude-code-templates@latest --command deployment/setup-automated-releases

2Manually: put the files in place

.claude/commands/setup-automated-releases.md

Call it with /setup-automated-releases. For all projects use ~/.claude/commands/

Questions about setup-automated-releases

How do I install setup-automated-releases in Claude Code?

Run npx claude-code-templates@latest --command deployment/setup-automated-releases, then use .claude/commands/setup-automated-releases.md.

What does setup-automated-releases do?

It configures version tracking, conventional commits, release and PR-check workflows, changelog updates, and GitHub Releases.

When does the automated release run?

The generated workflow runs after a push to main. It reviews commits since the previous release, selects the version bump, and creates a GitHub Release.

Source text

setup-automated-releases.md · MIT
---
allowed-tools: Read, Write, Edit, Bash
argument-hint: "[release-type] | --semantic | --conventional-commits | --github-actions | --full-automation"
description: Setup automated release workflows with semantic versioning, conventional commits, and comprehensive automation
---

# Automated Release System

Setup automated release workflows: $ARGUMENTS

## Current Project Analysis

- Project structure: @package.json or @setup.py or @go.mod (detect project type)
- Existing workflows: !`find .github/workflows -name "*.yml" 2>/dev/null | head -3`
- Current versioning: @package.json version or git tags analysis
- Commit patterns: !`git log --oneline -20 | grep -E "^(feat|fix|docs|style|refactor|test|chore)" | wc -l || echo "0"` conventional commits
- Release history: !`git tag -l | wc -l || echo "0"` existing releases

## Task

Implement comprehensive automated release system:

1. **Analyze Repository Structure**
   - Detect project type (Node.js, Python, Go, etc.)
   - Check for existing CI/CD workflows
   - Identify current versioning approach
   - Review existing release processes

2. **Create Version Tracking**
   - For Node.js: Use package.json version field
   - For Python: Use __version__ in __init__.py or pyproject.toml
   - For Go: Use version in go.mod
   - For others: Create version.txt file
   - Ensure version follows semantic versioning (MAJOR.MINOR.PATCH)

3. **Set Up Conventional Commits**
   - Create CONTRIBUTING.md with commit conventions:
     - `feat:` for new features (minor bump)
     - `fix:` for bug fixes (patch bump)
     - `feat!:` or `BREAKING CHANGE:` for breaking changes (major bump)
     - `docs:`, `chore:`, `style:`, `refactor:`, `test:` for non-releasing changes
   - Include examples and guidelines for each type

4. **Create Pull Request Template**
   - Add `.github/pull_request_template.md`
   - Include conventional commit reminder
   - Add checklist for common requirements
   - Reference contributing guidelines

5. **Create Release Workflow**
   - Add `.github/workflows/release.yml`:
     - Trigger on push to main branch
     - Analyze commits since last release
     - Determine version bump type
     - Update version in appropriate file(s)
     - Generate release notes from commits
     - Update CHANGELOG.md
     - Create git tag
     - Create GitHub Release
     - Attach distribution artifacts
   - Include manual trigger option for forced releases

6. **Create PR Validation Workflow**
   - Add `.github/workflows/pr-check.yml`:
     - Validate PR title follows conventional format
     - Check commit messages
     - Provide feedback on version impact
     - Run tests and quality checks

7. **Configure GitHub Release Notes**
   - Create `.github/release.yml`
   - Define categories for different change types
   - Configure changelog exclusions
   - Set up contributor recognition

8. **Update Documentation**
   - Add release badges to README:
     - Current version badge
     - Latest release badge
     - Build status badge
   - Document release process
   - Add link to CONTRIBUTING.md
   - Explain version bump rules

9. **Set Up Changelog Management**
   - Ensure CHANGELOG.md follows Keep a Changelog format
   - Add [Unreleased] section for upcoming changes
   - Configure automatic changelog updates
   - Set up changelog categories

10. **Configure Branch Protection**
    - Recommend branch protection rules:
      - Require PR reviews
      - Require status checks
      - Require conventional PR titles
      - Dismiss stale reviews
    - Document recommended settings

11. **Add Security Scanning**
    - Set up Dependabot for dependency updates
    - Configure security alerts
    - Add security policy if needed

12. **Test the System**
    - Create example PR with conventional title
    - Verify PR checks work correctly
    - Test manual release trigger
    - Validate changelog generation

Arguments: $ARGUMENTS

### Additional Considerations

**For Monorepos:**
- Set up independent versioning per package
- Configure changelog per package
- Use conventional commits scopes

**For Libraries:**
- Include API compatibility checks
- Generate API documentation
- Add upgrade guides for breaking changes

**For Applications:**
- Include Docker image versioning
- Set up deployment triggers
- Add rollback procedures

**Best Practices:**
- Always create release branches for hotfixes
- Use release candidates for major versions
- Maintain upgrade guides
- Keep releases small and frequent
- Document rollback procedures

This automated release system provides:
- ✅ Consistent versioning
- ✅ Automatic changelog generation
- ✅ Clear contribution guidelines
- ✅ Professional release notes
- ✅ Reduced manual work
- ✅ Better project maintainability

© davila7 · MIT · davila7/claude-code-templates

Similar slash commands

All slash commands for DevOps and infrastructure →

From the same set745

The whole set →
github-actions-creator github-actions-creator inspects project structure to generate production-ready GitHub Actions YAML files for test pipelines, Docker builds, and deployment. CX Codex +1 352installs log The /orchestration/log command sends task completion reports to Linear, Obsidian, Jira or GitHub Issues. Triggered manually after finishing a task or at day's end for a summary. CX Codex +1 351installs create-worktrees create-worktrees — a command for Claude Code fetches all open PRs through GitHub CLI and creates a git worktree for each branch in ./tree/<BRANCH_NAME>. Multiple PRs can be reviewed or worked on in parallel, each in its own directory. CX Codex +1 351installs test-automation-orchestrator The test-automation-orchestrator command inspects test files and project configuration, then helps plan parallel, sequential, or conditional test runs and CI/CD pipeline execution. CX Codex +1 350installs setup-ci-cd-pipeline setup-ci-cd-pipeline configures CI/CD pipelines for GitHub Actions, GitLab CI, Azure Pipelines, or Jenkins with automated testing, security gates, and deployment flows. CX Codex +1 346installs screenshot-synthesizer screenshot-synthesizer merges UI, interaction, and business analysis results into a single Markdown development task checklist. CX Codex 346installs scientific-brainstorming scientific-brainstorming turns Claude Code into a research partner for scientific ideation. Useful when formulating novel hypotheses or spotting cross-disciplinary links. CX Codex +1 345installs excalidraw This skill routes Excalidraw file work to subagents so large JSON diagrams stay out of the main context. Use it for flowcharts and architecture visuals. CX Codex +1 342installs

Project sponsors

Companies that keep this analytics open