R Package Release Checklist FAQs

Question 1

Does this skill work with any programming language?

Accepted Answer

No, this specific skill is purpose-built for R programming. It requires an R package structure with a DESCRIPTION file and the usethis R package installed.

Question 2

Do I need the GitHub CLI installed to use this skill?

Accepted Answer

The gh CLI is recommended for the best experience as it allows the skill to automatically create the GitHub issue for you. If it's not available, the skill will provide the Markdown content for you to create the issue manually.

Question 3

Does it handle R development version numbers like 0.1.0.9000?

Accepted Answer

Yes, the skill is designed to recognize R-style development suffixes (.9xxx) and will strip them appropriately when calculating the next stable release version.

Question 4

How does the skill suggest the next version number?

Accepted Answer

The skill reads your package's DESCRIPTION file for the current version and parses the NEWS.md file. If it detects keywords like 'breaking changes', it suggests a Major release; 'bug fixes' suggests a Patch; and new features suggest a Minor release.

Question 5

Can I modify the checklist before it gets posted to GitHub?

Accepted Answer

Yes, the skill includes a customization step where it displays the generated checklist and asks if you'd like to add, remove, or reword any items before finalizing the issue.

R Package Release Checklist

主要功能

使用场景

R Package Release Checklist

主要功能

使用场景