What is plastic-releasing?

A release workflow for projects that merges a feature branch, updates the version, creates an annotated Git tag, pushes changes, and runs configured publishing steps. Semantic versioning uses version numbers to describe compatible and breaking releases.

Use it to release a project, tag a version, or ship changes through the configured merge, verification, publishing, and cleanup process.

It provides a defined sequence and checks for version mismatches, unfinished tests, incorrect stable versions, and unsynchronized release destinations.

plastic-releasing — Skill for Claude Code by zalom

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add zalom/plastic --skill releasing

Clone the repo

git clone --depth 1 https://github.com/zalom/plastic

Made for: Claude Code.

Or install plastic, the plugin that ships this one along with the rest of its 36 skills, 10 agents, 5 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zalom/plastic/releasing.svg)](https://agentmods.dev/skills/zalom/plastic/releasing)

Your own site

<a href="https://agentmods.dev/skills/zalom/plastic/releasing"><img src="https://agentmods.dev/badge/skills/zalom/plastic/releasing.svg" alt="Measured on agentmods" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,878 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00038	$0.03878
Opus 5	$0.00019	$0.01939
Sonnet 5	$0.00008	$0.00776
Haiku 4.5	$0.00004	$0.00388

Measured 6d ago against content hash 3a0aceb967e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

plastic-releasing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/releasing/SKILL.md · 339 lines

How it starts

The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Releasing

Merge, bump, tag, push. Annotated tags with changelogs. Semantic versioning. Project configuration drives the workflow - no hardcoded assumptions.

Checklist

Read project config
All tests pass (or verification skipped per config)
Merge feature branch to main
Bump version in configured version files
Stable-cut guard passes (version files agree, no pre-release suffix; stable/latest cuts only)
Commit version bump
Create annotated tag
Push to remote with tags
Run post-push actions (GitHub release, npm publish, etc.)
Verify release sync (npm dist-tag, GitHub "Latest", git tag all show the new version)
Clean up the intent's worktrees (merge-then-remove)
Complete active intent

Workflow

0. Read Project Config

Before anything else, determine which project we are releasing and load its config.

Read ~/.plastic/projects.yml - find the project whose path matches the current working directory.
Extract the project slug (the key under projects:).
Read ~/.plastic/projects/{slug}/project.yml - this contains the release: section.

Expected release: keys in project.yml:

release:
  verify: "bin/rails test"              # command to run before release
  version_file: package.json            # single file containing the version
  version_files:                        # multiple files (overrides version_file)
    - package.json                      # list EVERY file carrying the version;
    - .claude-plugin/plugin.json        # they must all be bumped together or they drift
    - .claude-plugin/marketplace.json
  tag_format: "v{{version}}"            # tag naming pattern ({{version}} is replaced)
  on_green:                             # actions to run after push succeeds
    - github_release
    - npm_publish
  on_complete: commit_and_push          # what to do with the version bump commit
  on_red: stop                          # what to do if verification fails

Read the full file on GitHub · 339 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 339 lines · 38 tokens per session scan A 3a0aceb967e7

Subscribe to this mod's changes

plastic-releasing is a skill published in the GitHub repository zalom/plastic (10 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 3,878 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Git and workflow Releases ai-agents ai-coding developer-tools intent-driven project-memory

memstack-development-changelog-generator

Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.

cwinvestments/memstack · 63 tokens

ijfw-ship

Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…

FerroxLabs/ijfw · 139 tokens

ijfw-preflight

Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'.

FerroxLabs/ijfw · 47 tokens

plate

Turn finished local work into a commit, an ordinary pull request, or a pull request stack. Use this skill to commit changes or to publish a branch. Use it to open or update a pull request. Use it to create, sync, restack, or submit a pull request stack. You can also run /plate. This skill owns all staging, commits…

paulnsorensen/easy-cheese · 106 tokens

ship

Use when code is ready to ship — creates PRs, merges, deploys, and verifies. Handles the full PR-to-production pipeline. Triggers on /ship.

garagon/nanostack · 36 tokens

finishing-a-development-branch

Use when implementation is complete, tests pass, and you need to decide the integration path. Also use when asked to prepare a branch for release: 'update changelog', 'bump version', 'bump patch version', 'make sure changelog is correct', 'make sure version is correct'. Triggers: 'done with this branch', 'ready to…

axiomantic/spellbook · 134 tokens