Skip to content
TrustedSkillsbeta
Back to all skills

Release Please

Checked
zenobi-us·vlatest·devops·MIT

Automatically generates a `release-please` pull request to update dependency versions and fix vulnerability warnings, streamlining your releases.

Repository

Install on your platform

This skill no longer installs under the name release-please. zenobi-us/dotfiles no longer contains any SKILL.md.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

zenobi-us

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 zenobi-us/dotfiles at b8fd7910f5.

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

Commit
b8fd7910f5
Manifest
files/devtools/agent/bundles/developer/skills/devtools/release-please/SKILL.md
Scanned
5 files, 453 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

The release-please skill automates the process of creating and publishing software releases. It handles version bumping, generating changelogs, and triggering deployments based on configured workflows. This reduces manual effort and ensures consistent release practices for projects.

When to use it

  • Automate release creation for open-source projects following semantic versioning.
  • Generate a detailed changelog automatically from commit messages.
  • Trigger deployment pipelines upon successful tag creation in your repository.
  • Standardize the release process across multiple repositories within an organization.

Key capabilities

  • Semantic Versioning (SemVer) support
  • Automated Changelog Generation
  • Workflow Integration (e.g., GitHub Actions)
  • Tag Creation and Management

Example prompts

  • "Create a new release based on the latest commits."
  • "Generate a changelog for version 1.2.3."
  • "Trigger the deployment pipeline after tagging the repository with v1.0.0."

Tips & gotchas

  • Requires proper commit message formatting adhering to conventional commits standards for accurate changelog generation.
  • Configuration typically involves setting up a workflow file (e.g., GitHub Actions) and defining release branches.