Skip to content
TrustedSkillsbeta
Back to all skills

Release Management

Checked
sgcarstrends·vlatest·devops·MIT

Automates software release deployment and rollback processes for sgcarstrends applications, ensuring stability and efficiency.

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 motormetrics/motormetrics --skill release-management -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

sgcarstrends

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 sgcarstrends/sgcarstrends at d852d8c519.

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

Commit
d852d8c519
Manifest
.agents/skills/release-management/SKILL.md
Scanned
2 files, 168 lines
Copies in repo
2 — all of them scanned
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 software release deployment and rollback processes specifically for sgcarstrends applications, ensuring stability and efficiency. It leverages semantic-release to manage versioning using a unified "v" prefix (e.g., v4.46.0), automatically updates CHANGELOG.md and package.json files across the monorepo, creates Git tags and GitHub Releases with auto-generated notes, and triggers Vercel deployments. Commits to the main branch trigger this automated release process.

When to use it

  • When deploying new versions of sgcarstrends applications.
  • To ensure consistent versioning across a monorepo project.
  • For automating changelog generation and GitHub Release creation.
  • To streamline the software release workflow, reducing manual effort.
  • When needing to quickly view recent releases or check the status of a release workflow.

Key capabilities

  • Automated semantic versioning (e.g., v4.46.0).
  • Automatic CHANGELOG.md updates.
  • Unified version management across a monorepo.
  • GitHub Release creation with auto-generated notes.
  • Vercel deployment triggered by release events.
  • Uses conventional commits for version bump analysis.

Example prompts

  • "Show me the last 5 releases."
  • "What's the status of the release workflow?"
  • "View the logs for the most recent release attempt."

Tips & gotchas

  • Commit messages must adhere to the conventional commits format for version bumps to be calculated correctly. Refer to the conventional-commits skill for details.
  • The release process is triggered by commits pushed to the main branch.
  • Debugging failures involves checking GitHub Actions logs and verifying commit types and message formatting.