Skip to content
TrustedSkillsbeta
Back to all skills

Release Please Protection

Checked
laurigates·vlatest·devops·MIT

This skill prevents accidental `release-please` updates, safeguarding your releases and ensuring stability by controlling automated changes.

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-protection -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-protection/SKILL.md
Scanned
3 files, 1,253 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 enables AI agents to safely manage release automation workflows by integrating with Release Please. It prevents unauthorized or accidental version bumps and ensures that only verified changes trigger new releases in your repository.

When to use it

  • You need to automate semantic versioning without risking manual errors.
  • Your team requires strict controls over when a new release is created.
  • You want to integrate release logic directly into an AI agent's workflow.
  • You are managing multiple repositories and need consistent release policies.

Key capabilities

  • Integrates with Release Please for automated version management.
  • Provides protection mechanisms against unintended release triggers.
  • Validates changelog entries before generating a new release.
  • Supports standard CI/CD pipeline workflows.

Example prompts

  • "Generate a Release Please configuration file that protects against accidental major version bumps."
  • "Review the latest commit changes and determine if a protected release should be triggered based on our policy."
  • "Create a script that uses this skill to verify changelog entries before allowing a release to proceed."

Tips & gotchas

Ensure your repository already has Release Please configured before using this protection layer. This skill acts as a safeguard, so it cannot override existing manual release commands if they bypass the agent's execution context.