release-check

Audit merged pull requests since a release tag and recommend a semantic version bump.

927|462|Updated Dec 23, 2010
One-click install
npx skills add https://github.com/ruby/rdoc --skill release-check-ruby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-check
Source: https://github.com/ruby/rdoc/tree/main/.claude/skills/release-check
Command: npx skills add https://github.com/ruby/rdoc --skill release-check-ruby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious process of auditing pull requests for a new release, ensuring proper labeling and recommending an appropriate version bump.

Core Features & Use Cases

  • Automated PR Audit: Scans merged PRs since the last release tag.
  • Label Verification: Checks if PRs have appropriate labels (bug, enhancement, documentation) based on content.
  • Version Bump Recommendation: Suggests a SemVer version bump (Major, Minor, Patch) with clear reasoning.
  • Use Case: Before releasing a new version of a software project, use this Skill to quickly identify any PRs that might have been missed, ensure they are correctly categorized, and get an informed suggestion for the next version number.

Quick Start

Run the release-check skill to audit pull requests and get a version bump recommendation.

Frequently Asked Questions about release-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit GitHub pull requests to recommend a semantic version bump?

You can audit merged GitHub pull requests and recommend a semantic version bump by scanning PRs since a specified release tag, verifying labels like bug or enhancement, and grouping them to suggest a Major, Minor, or Patch update.

How do I determine the correct semver bump for my new GitHub release?

To determine the correct semver bump for a GitHub release, analyze merged pull requests since the last tag to verify labels such as bug, enhancement, and documentation, which dictate whether the version bump is Major, Minor, or Patch.

Can I automatically suggest labels for unlabelled pull requests based on their titles and descriptions?

Yes, you can automatically suggest labels for unlabelled pull requests by analyzing PR titles and descriptions to identify relevant categories like bug, enhancement, or documentation for a comprehensive release overview.

What is the best way to categorize merged pull requests by label for a release audit?

The best way to categorize merged pull requests by label for a release audit is to scan PRs since the last release tag, verify existing labels, analyze content for missing labels, and group PRs by label for a comprehensive overview.

Does this automated PR audit require specific release tags to function correctly?

Yes, the automated PR audit requires a specified release tag to function correctly, as it scans and evaluates only the pull requests that have been merged since that specific release tag was created.

Why should I verify PR labels before generating a semantic versioning recommendation?

You should verify PR labels before generating a semantic versioning recommendation because labels like bug, enhancement, and documentation directly inform whether the version bump should be Major, Minor, or Patch.