r-xla-release

Automate R package release preparation from DESCRIPTION and NEWS.md.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/r-xla/claude-config --skill r-xla-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: r-xla-release
Source: https://github.com/r-xla/claude-config/tree/main/skills/r-xla/release
Command: npx skills add https://github.com/r-xla/claude-config --skill r-xla-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replaces manual, error-prone package release steps with an automated, repeatable workflow that validates package structure, updates metadata, and prepares release artifacts.

Core Features & Use Cases

  • Validate that the working directory is an R package by checking for a DESCRIPTION file and optional Remotes entries.
  • Compute and apply a release type (Major/Minor/Patch) based on NEWS.md entries, then update DESCRIPTION and NEWS.md accordingly.
  • Create a release branch, commit changes, push, and open a PR, then tag the release and prepare for a GitHub release.

Quick Start

From the root of an R package, run this skill to prepare a release PR and update DESCRIPTION and NEWS.md.

Frequently Asked Questions about r-xla-release

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

FAQPage Schema
How do I automate an R package release from the root directory?

Automated R package release workflows analyze your DESCRIPTION and NEWS.md files to compute a version bump, update metadata, create a release branch, and open a pull request directly from the root directory.

How does CI determine the correct version bump for an R package?

CI workflows determine the correct version bump by analyzing NEWS.md entries to compute whether a Major, Minor, or Patch release is needed, then updating DESCRIPTION and NEWS.md files accordingly.

Can I use this workflow to release an R package with Remotes dependencies?

Yes, you can use this workflow with Remotes dependencies; the Skill validates your package structure by checking the DESCRIPTION file and identifying optional Remotes entries before proceeding with release steps.

What is the best way to prepare a release branch and PR for an R package?

The best way to prepare a release branch and PR is to use an automated workflow that updates DESCRIPTION and NEWS.md, commits the changes, pushes the release branch, and opens a pull request with guided user prompts.

Does the R package release workflow require manual intervention before pushing changes?

The R package release workflow requires manual intervention through guided user prompts to ensure safe release steps are followed before it pushes changes or tags the release on your behalf.

Why does my automated R package release workflow check for a DESCRIPTION file?

Automated R package release workflows check for a DESCRIPTION file to validate that the current working directory is an actual R package before initiating any release preparation steps or metadata updates.