Setup Tagpr
Automates release management by creating pull requests for pending updates, tagging merged commits, and generating GitHub Releases with semantic versioning.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Automated creation and updates of release pull requests for unreleased items
- Support for immutable releases using draft GitHub Release configurations
- Semantic versioning suggestions based on commit history and pull request labels
- Automatic synchronization of version numbers across multiple configuration files
- Tailored setup workflows for Go (goreleaser) and TypeScript/Node.js projects
Use cases
- Configuring automated version tagging for Go projects using goreleaser
- Introducing automated release management to a new or existing repository
- Setting up a release workflow for TypeScript or Node.js packages
FAQ
When should I use the Setup Tagpr skill?
You should use this skill when you want to implement a professional release workflow without manual intervention. It is ideal for Go projects using goreleaser, TypeScript/Node.js projects needing version file synchronization, or any repository requiring automated semantic versioning.
Does it support multi-file version synchronization?
Yes. One of the key capabilities of this skill is configuring tagpr to update version strings across multiple files simultaneously, such as package.json and manifest.json, ensuring consistency across your entire project.
What does the Setup Tagpr Claude Code skill do?
This skill automates the configuration of tagpr within your repository. It sets up a system that automatically creates release pull requests for unreleased changes, calculates semantic versioning, tags commits upon merging, and generates official GitHub Releases.
Why is a GitHub Personal Access Token (GH_PAT) required?
A GH_PAT is necessary because the default GITHUB_TOKEN provided by GitHub Actions cannot trigger subsequent workflows. Using a PAT ensures that when tagpr pushes a new tag, your release or deployment workflows are successfully triggered.
How does this skill handle semantic versioning (SemVer)?
The skill configures tagpr to suggest version bumps based on GitHub labels. By applying 'major' or 'minor' labels to pull requests, the tool automatically calculates the next version; otherwise, it defaults to a patch increment.
Related skills
ActivityPub PR Workflow
Enforces a standardized pull request lifecycle, including branch naming, changelog entries, and reviewer assignments for the ActivityPub for WordPress project.
Deployment Devops55512 ptsCommonTools CLI
Manages the lifecycle of recipes and charms within the Common Fabric framework, including deployment, data manipulation, and reactive linking.
Deployment Devops2312 ptsGit Workflow
Guides developers on Git workflow best practices for creating clean commits, naming branches, and automating changelogs.
Deployment Devops412 pts