More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Release Packets: numbered releases you can always roll back

    1

    Every release becomes a numbered zip that is never overwritten, holding only what ships, with a git save point right before and right after.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Release Packets: numbered releases you can always roll back

    Release Packets: numbered releases you can always roll back

    Example session with this skill installed

    My shop site is ready to ship with the new price list page. Make the next release packet. Earlier packets are in ../packets. A teammate is also working in this folder.

    • Read your context and instructions
    • Compiled the release packets

    Packet 02 is built: 02-shop-2026-10-23-price-list.zip, in ../packets/.

    What I checked first

    • ls ../packets at build time: the newest was 01-shop-2026-10-20-first-launch.zip, so this one is 02.
    • git status --short showed three changes: index.html, prices.html (new) and about.html.
    • about.html is not part of this release. It is your teammate's unfinished edit, so I left it out and did not touch it.

    What changed since packet 01

    • added: prices.html
    • changed: index.html
    • same: style.css

    Save points

    • Before: ee49a15 Before packet 02: price list page (pushed)
    • After: c23b350 Ship packet 02: price list (pushed; an empty commit, since the build changed nothing in the project)

    What is inside packet 02

    • .well-known/security.txt (the site needs it)
    • about.html (as last saved, not the draft)
    • index.html
    • prices.html
    • style.css

    Left out

    • .env (secrets file)
    • notes.md (working notes)
    • .git, .gitignore

    Checks

    • Packet 01 is untouched: same fingerprint before and after (29ea6aa5c637fdd1).
    • Your teammate's edit to about.html is still uncommitted, exactly as they left it.

    To roll back: packet 01 is 01-shop-2026-10-20-first-launch.zip, and commit 83d0c7d Ship packet 01: first launch rebuilds it.

    Nothing was uploaded or deployed. Say yes to packet 02 if you want it live.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A folder of final.zip, final2.zip and new-final.zip cannot tell you what is live or how to get back to the last good one. Release Packets has your agent give every release a number, a date and a short label; check right before building for changes it did not make; save the project to git; build a zip holding only what ships (no notes, settings, keys or dot-folders unless you name one the product needs); check what is inside; then save again with the packet number in the message. "What shipped?" and "put the last good one back" each get a one-line answer.

    It never overwrites or deletes a packet, and never uploads or deploys without your yes.

    Tested on a practice website with a fake secrets file, working notes, a folder the site needs and a teammate's unfinished file: the packet held exactly what should ship, and the earlier packet was untouched.

    Instructions only: no scripts, nothing installed. The only thing it sends is your own git push.

    Created by Greygray, with AI collaboration openly included in the process.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Needs a project in git. It does not upload or deploy anything; it asks first, and only on your yes. It never deletes old packets, so the packet folder grows until you clear it out yourself. It needs a script or tool that writes forward-slash paths in the zip (on Windows, Python's zipfile works; some built-in zip tools do not). A project with no git remote gets its save points as local commits only.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 27 days ago

    Software
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access

    Terminal / Shell: runs git (status, commit, push) and the project's own build step. Read Files: lists the packet folder and compares the project with the last packet. Write Files: writes the new zip into the packet folder; it never overwrites or deletes one. Network Access: pushes the git save points to your own remote, nothing else.

    Listed27 days ago
    Updated22 days ago

    What's inside

    Frequently Asked Questions

    Every release gets the next number, the date and a short label, like 02-shop-2026-10-23-price-list.zip. The number is taken from the packet folder right before the build, and a packet is never overwritten. A git save point before and after carries the same number, so you can always tell which code became which zip.

    Yes. It leaves out every path that starts with a dot (.env, .git, .vscode and the like) unless you name one the product needs, such as a website's .well-known folder. It also leaves out working notes, logs, local settings and test data the product does not need. Then it lists what is inside the zip and checks nothing from that list got in.

    Any project kept in git, in any language. It runs the project's own build step if there is one. Your agent needs a terminal to run git and a way to write a zip with forward-slash paths.

    Git, and an agent that can run terminal commands and read and write files. A git remote is needed only if you want the save points pushed.

    No. It never uploads or deploys a packet unless you say yes to that packet. It builds the packet, saves the project to git, and tells you where the packet is.

    New in DevOps & Cloud