Finish Release

Name: Finish Release
Author: fradser

Checked

fradser·vlatest·devops·MIT

Automatically completes a release by triggering final steps like deployments and notifications, streamlining DevOps workflows for faster releases.

Repository

Install on your platform

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

Run this in your project

terminal

$ npx skills add fradser/dotclaude --skill finish-release -a claude-code

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

fradser

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 30 Sept 2026

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 fradser/dotclaude at 9815c4f485.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 9815c4f485
Manifest: git/skills/finish-release/SKILL.md
Scanned: 1 file, 18 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 finish-release skill automates and streamlines the final steps of a software release process. It handles tasks like updating deployment manifests, triggering pipelines, and notifying relevant teams about the completed release. This ensures releases are consistent, reliable, and require minimal manual intervention.

When to use it

After code merges and testing are complete, but before production deployment.
To automate the final steps of a release in CI/CD pipelines.
When needing to consistently update multiple environments (staging, QA, production) during a release.
For ensuring notifications are sent automatically upon successful release completion.

Key capabilities

Manifest updates
Pipeline triggering
Team notifications

Example prompts

"Finish the release for project 'Phoenix' to staging."
"Trigger the deployment pipeline after updating manifests for version 1.2.3."
"Notify the operations team that the release is complete."

Tips & gotchas

The skill requires appropriate permissions within your CI/CD environment and notification channels to function correctly. Ensure these are configured before use for optimal results.