Skip to content
TrustedSkillsbeta
Back to all skills

Release Please Pr Workflow

Checked
laurigates·vlatest·devops·MIT

Automates PR merging and release workflows, streamlining deployments based on LaurieGates' defined rules and approvals.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add laurigates/claude-plugins --skill release-please-pr-workflow -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

laurigates

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned laurigates/claude-plugins at 45d1d7dcf6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
45d1d7dcf6
Manifest
git-plugin/skills/release-please-pr-workflow/SKILL.md
Scanned
1 file, 252 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates the process of creating and merging pull requests for software releases. It analyzes commit messages to determine version numbers, generates release notes based on those commits, and then creates a new branch with updated files ready for review and merge. This streamlines the release workflow by reducing manual effort and potential errors.

When to use it

  • You're managing a project with frequent software releases and want to automate the pull request creation process.
  • Your team follows semantic versioning (e.g., feat: add new feature or fix: resolve bug).
  • You need to generate release notes automatically based on commit messages.
  • You're looking for a way to standardize your release workflow and reduce the risk of human error.

Key capabilities

  • Analyzes commit messages to determine version numbers.
  • Generates release notes from commit messages.
  • Creates new branches for releases.
  • Automatically creates pull requests based on generated changes.

Example prompts

  • "Create a release PR."
  • "Generate a release branch and pull request for the latest commits."
  • "Prepare a release with version number X.Y.Z from current state."

Tips & gotchas

  • Requires a project using semantic versioning commit messages to function correctly.
  • Ensure your repository is properly configured with appropriate access permissions for automated branch creation and pull request generation.