create-release-checklist
Skill2 starsChanged 6 months agoMITView on GitHub
Create a release checklist and GitHub issue for an R package. Use when the user asks to "create a release checklist" or "start a release" for an R package.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- BrightGold70/skillsword for word, first seen Nov 8, 2026
- software-mansion/smeltertheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 1
- BrightGold70/skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 1
- software-mansion/smelter★ 740same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alt-textSkill
- brand-ymlSkill
- cliSkill
- cran-extrachecksSkill
- critical-code-reviewerSkill
- describe-designSkill
- ggsqlSkill
- implementSkill
- maintainer-declineSkill
- miraiSkill
- pr-createSkill
- pr-threads-addressSkill
- pr-threads-resolveSkill
- quarto-authoringSkill
- r-cli-appSkill
- release-postSkill
- review-testingSkill
- r-package-developmentSkill
- shiny-bslibSkill
- shiny-bslib-themingSkill
- testing-r-packagesSkill
- working-onSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 12 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 46
Check that the working directory contains a file called DESCRIPTION.
- Very specific: line 49
Use Rscript -e 'utils::packageVersion("usethis")' to check if the usethis package is installed.
- Very specific: line 54
If gh is not installed, try running git remote -v to find a GitHub URL.
- Very specific: line 55
If the local repo does not have a GitHub remote, suggest the user connect the package to GitHub using usethis::use_github().
- Very specific: line 58
If gh is installed but not authenticated and the repo has a GitHub remote, suggest that the user run gh auth login.
- Distinctive: line 61
If any check fails, inform the user of the specific issue with clear instructions on how to fix it, then stop the workflow.
- Distinctive: line 74
If the NEWS mentions "breaking changes", "breaking", "BREAKING", or similar language, suggest a Major release.
- Distinctive: line 76
If the NEWS mentions only "bug fixes", "fixes", "patch", or similar language with no new features, suggest a Patch release.
- Distinctive: line 124
Read the generated checklist (which is Markdown) and display it to the user.
- Distinctive: line 128
Use the AskUserQuestion tool to ask:
- Distinctive: line 136
If the user wants to customize the checklist, enter an iterative refinement loop:
- Distinctive: line 138
Ask: "Suggest items that should be added or any items that can be safely removed, or confirm that there are no more changes requested."
- Distinctive: line 144
Ask: "Does this look good or do you have more suggestions?"
- Distinctive: line 145
If the user has more suggestions, go back to step 2.
- Very specific: line 185
If the GitHub issue creation fails (when using gh), check for common issues:
- Very specific: line 187
Authentication errors: Ensure gh auth status shows the user is logged in.
- Very specific: line 190
Check with gh repo view to verify they have the correct permissions.
- Distinctive: line 191
Network errors: If there are connectivity issues, suggest retrying the command or checking their internet connection.
- Distinctive: line 193
Invalid Markdown: If the issue body has formatting errors, verify the checklist Markdown is properly formatted with valid syntax.
- Distinctive: line 196
If the issue creation fails, preserve the checklist content and offer to:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create an R Package Release Checklist
Generate a release checklist for an R package and create the corresponding GitHub issue.
Overview
This skill guides you through creating a R package release checklist issue on GitHub by:
- Determining the current version and prompting for release type.
- Generating an initial checklist.
- Prompting the user for additional customization.
- Creating a GitHub issue from the final checklist.
Prerequisites
- The working directory must be an R package with a
DESCRIPTIONfile at the root. - The
usethisR package must be available.
And to enable automatic issue creation:
- The
ghCLI must be installed and authenticated. - The R package must be associated with a GitHub repository.
Workflow
Step 1: Validation
First, check that the prerequisites are available (in this order for efficiency):
- Check that the working directory contains a file called
DESCRIPTION. If not, inform the user that this must be run from an R package root directory and stop. - Use
Rscript -e 'utils::packageVersion("usethis")'to check if theusethispackage is installed. If not, instruct the user to install it withinstall.packages("usethis"), then stop. - Determine the GitHub URL for the repository, if one exists. First try
gh repo view --json url. If that fails, diagnose the error:- If
ghis not installed, try runninggit remote -vto find a GitHub URL. - If the local repo does not have a GitHub remote, suggest the user connect
the package to GitHub using
usethis::use_github(). Offer to run this command for the user; if they decline, continue without a GitHub URL. - If
ghis installed but not authenticated and the repo has a GitHub remote, suggest that the user rungh auth login.
- If
If any check fails, inform the user of the specific issue with clear instructions on how to fix it, then stop the workflow. Do not proceed to the next step until all prerequisites are met.
Step 2: Initialization
Next, you need to determine the current package's name and version. Read the
DESCRIPTION file and extract the Version: and Package: fields from it.
Then, check if a NEWS.md file exists. If it does, read the first section
(typically the most recent unreleased changes) to understand what kind of
changes have been made. Use this to suggest an appropriate release type:
- If the NEWS mentions "breaking changes", "breaking", "BREAKING", or similar language, suggest a Major release.
- If the NEWS mentions only "bug fixes", "fixes", "patch", or similar language with no new features, suggest a Patch release.
- Otherwise (new features, improvements, enhancements), suggest a Minor release.
Display the current version to the user and ask them what type of release this should be using the AskUserQuestion tool. Make the suggested release type the first option with "(Recommended)" appended to the label:
Question: "What type of release is this?" Header: "Release type" Options (with recommended option first):
- Major (X.0.0) - Breaking changes (add "(Recommended)" if suggested)
- Minor (x.X.0) - New features but without breaking changes (add "(Recommended)" if suggested)
- Patch (x.x.X) - Bug fixes only (add "(Recommended)" if suggested)
Calculate the new version by manipulating the current version according to the user's answer. For example:
- Current version
1.2.3+ Major release →2.0.0 - Current version
1.2.3+ Minor release →1.3.0 - Current version
1.2.3+ Patch release →1.2.4 - Current version
0.2.1.9000+ Patch release →0.2.2 - Current version
0.2.1.9003+ Minor release →0.3.0
Note: If the current version ends in .9xxx (R-style development versions),
strip that suffix before calculating the new version.
Display: "Preparing release checklist for ${PACKAGE_NAME} ${CURRENT_VERSION} → ${NEW_VERSION}".
Step 3: Checklist Generation
Generate an initial checklist using the scripts/generate_checklist.R script
included with this skill:
# If the GitHub URL is known:
Rscript "${SKILL_DIR}/scripts/generate_checklist.R" "${NEW_VERSION}" "${GITHUB_URL}"
# Otherwise:
Rscript "${SKILL_DIR}/scripts/generate_checklist.R" "${NEW_VERSION}"(Where ${SKILL_DIR} represents the directory where this skill is installed.)
Ignore any "Setting active project..." lines in the output.
Read the generated checklist (which is Markdown) and display it to the user.
Step 4: User Customization
Use the AskUserQuestion tool to ask:
Question: "Would you like to customize the checklist before creating the issue?" Header: "Customize?" Options:
- No, create the issue as-is
- Yes, let me customize it
If the user wants to customize the checklist, enter an iterative refinement loop:
- Ask: "Suggest items that should be added or any items that can be safely removed, or confirm that there are no more changes requested."
- Based on the user's feedback, update the checklist (add items, remove items,
reword items, etc.). Keep the checklist in Markdown format with proper
checkbox syntax (
- [ ]for tasks). - Display the updated checklist to the user.
- Ask: "Does this look good or do you have more suggestions?"
- If the user has more suggestions, go back to step 2. If the user confirms it looks good, exit the loop and proceed to Step 5.
The checklist should be maintained as a Markdown string throughout this process so it can be easily passed to the GitHub issue creation command.
Step 5: GitHub Issue Creation
The final checklist should be formatted as Markdown with proper sections and checkboxes.
If gh is available and authenticated, use it to create the GitHub issue
yourself, passing the checklist content directly via stdin:
gh issue create \
--title "Release ${PACKAGE_NAME} ${NEW_VERSION}" \
--body-file - <<'EOF'
[checklist content here]
EOFThen show the user:
- A success message with the issue URL.
- The suggestion "You can now use the 'do-release-checklist' skill to walk through the checklist tasks." (Note: This is a companion skill that helps guide users through executing the checklist items. If this skill doesn't exist yet in your repository, you may omit this suggestion.)
If gh is not available, display the checklist to the user with
instructions to manually create a GitHub issue:
- Show the suggested issue title: "Release ${PACKAGE_NAME} ${NEW_VERSION}"
- Show the full checklist content formatted as Markdown.
- Instruct the user to copy the content and create the issue manually at their repository's issues page.
Error Handling
If the GitHub issue creation fails (when using gh), check for common issues:
- Authentication errors: Ensure
gh auth statusshows the user is logged in. Suggest runninggh auth loginif needed. - Repository permissions: The user must have write access to create issues.
Check with
gh repo viewto verify they have the correct permissions. - Network errors: If there are connectivity issues, suggest retrying the command or checking their internet connection.
- Invalid Markdown: If the issue body has formatting errors, verify the checklist Markdown is properly formatted with valid syntax.
If the issue creation fails, preserve the checklist content and offer to:
- Retry the command.
- Display the checklist for manual issue creation instead.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

