agentsclimarketplace
Sign in

Release prep

Skill lteawoo/skills/skills/release-prep

Review environment variables, migrations, config differences, rollback paths, and operational checklists before release. Use it to determine whether completed work is actually ready to ship.From its SKILL.md

Install
npx -y skills add lteawoo/skills --skill release-prep

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, 411 tokens by cl100k_base, as published. Nobody here has run it

Release Prep

Purpose

Check whether a completed feature or application can be deployed safely to production.

Core Principles

  1. Separate code quality from release readiness.
  2. Judge readiness from the production environment perspective, not the dev environment.
  3. Check environment variables, secrets, and network config differences first.
  4. Review data changes together with rollout order and rollback paths.
  5. Plan for recovery from failed deployments, not only successful ones.
  6. Do not leave operational steps vague or implicit.

Inputs

  • Description of the feature or app being released
  • Related code changes
  • Environment variables or deployment config
  • Database migration, seed, or backfill details
  • Target environments such as dev, staging, or prod
  • Monitoring, alerting, or rollback procedures, if available

Workflow

  1. Summarize the release scope and user impact in one line.
  2. Document environment-specific differences and required variables.
  3. Review database changes and rollout order.
  4. Check external dependencies and credential injection paths.
  5. List health checks, logs, and monitoring items to inspect after deployment.
  6. Define rollback or workaround steps for failure cases.

Output Format

Release Summary

  • Deployment target
  • User impact range

Pre-Release Checks

  • Required environment variables
  • Config or infrastructure changes
  • Readiness of external dependencies

Data Change Review

  • Whether migrations are involved
  • Rollout order
  • Whether backfill or data-integrity validation is required

Deployment Procedure

  • Tasks before deployment
  • Checks during deployment
  • Checks after deployment

Rollback and Response

  • Whether rollback is possible
  • Rollback steps
  • Workarounds during incidents

Key Risks

  • Operational outage risk
  • Configuration omission risk
  • Items that still need confirmation

When Information Is Missing

  • Split missing operational data into explicit follow-up items.
  • Treat unclear migration impact as elevated data risk.
  • Document any non-automated procedure as a manual checklist.

What ships with it: 1 file

2.2 KB alongside SKILL.md

Gives 0 of the 12 instructions most ship operate skills give in 411 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

  • Document a rollback plan before deploymentin 41 of 779, across 22 files
  • Update the changelogin 21 of 779, across 19 files
  • Run the test suitein 20 of 779
  • Create an annotated git tagin 20 of 779
  • Clean up feature flags after full rolloutin 18 of 779, across 10 files
  • Verify deployment health after launchin 18 of 779, across 10 files
  • Test both feature flag statesin 17 of 779, across 9 files
  • Verify the working tree is cleanin 17 of 779
  • Make database migrations backward-compatiblein 16 of 779, across 8 files
  • Set up error monitoring before launchin 15 of 779, across 7 files
  • Monitor metrics at each rollout stagein 14 of 779, across 5 files
  • Create a GitHub releasein 14 of 779

Said here and by no other author read

  • Judge readiness from the production perspective
  • Check environment variables and config differences first
  • Review data changes with rollback paths
  • Plan for recovery from failed deployments
  • Summarize release scope and user impact
  • Document environment-specific differences

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.