poly-and-release-workflow

poly-and-release-workflow is a skill for Claude Code from Goldziher/basemind. It costs 7 tokens per session (583 once invoked), scanned A, original, MIT.

A required checklist for checking a Rust project before committing or pushing changes. It combines formatting, code checks, tests, linting, and a broader test harness.

In plain words
What is it for?
Use it when preparing a change for review or release, including running tests against eight real open-source codebases.
Why use it?
It puts checks in an order that catches simple problems early and reduces the chance of shipping broken code or failed checks.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the basemind plugin — 15 skills, 10 commands, 6 agents, 2 hooks, 1 MCP server shipped together

Good fit Use it when preparing a change for review or release, including running tests against eight real open-source codebases.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/goldziher/basemind/poly-and-release-workflow
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 Goldziher/basemind --skill poly-and-release-workflow
Clone the repo
git clone --depth 1 https://github.com/Goldziher/basemind

Made for: Claude Code.

Or install basemind, the plugin that ships this one along with the rest of its 15 skills, 10 commands, 6 agents, 2 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.

agentmods badge for poly-and-release-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/goldziher/basemind/poly-and-release-workflow.svg)](https://agentmods.dev/skills/goldziher/basemind/poly-and-release-workflow)
Your own site
<a href="https://agentmods.dev/skills/goldziher/basemind/poly-and-release-workflow"><img src="https://agentmods.dev/badge/skills/goldziher/basemind/poly-and-release-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 7 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 583 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.00583
Opus 5 $0.00003 $0.00292
Sonnet 5 $0.00001 $0.00117
Haiku 4.5 $0.00001 $0.00058

Measured 8d ago against content hash c4ff618f48f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

poly-and-release-workflow 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 8d 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.

.ai-rulez/skills/poly-and-release-workflow/SKILL.md · 53 lines

How it starts

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

Poly + Release Workflow

The canonical order to run before pushing a change. Each step gates the next; do not skip.

Local check loop

cargo fmt
cargo clippy --workspace --all-targets --tests -- -D warnings
cargo test --workspace
poly lint .

Why this order:

  • cargo fmt first so clippy / poly don't fail on formatting.
  • Clippy strict (-D warnings) — surface real issues before the broader poly sweep.
  • Unit + integration tests catch logic regressions before the slow harness.
  • poly lint . is the meta-linter: typos, markdownlint (120-char cap), cargo-deny licenses, cargo-machete unused deps, rustdoc-lint, rust-max-lines (1000-line cap on src/**/*.rs).

Harden harness

After the local loop passes:

BASEMIND_HARDEN_NO_BUILD=1 \
  cargo test --release --test harden -- --ignored --nocapture \
  2>&1 | tee /tmp/basemind-harden-$(date +%s).log
  • BASEMIND_HARDEN_NO_BUILD=1 reuses target/release/basemind — saves ~30s per run. Drop it when you're suspicious the binary is stale.
  • Expect 8/8 green: ripgrep, tokio, typescript, react, django, requests, gin, ripgrep-shallow.
  • Canaries: tokio spawn_hits >= 200, django get_hits >= 200, react useState_hits >= 20, ripgrep-shallow any_truncated == true.

Commit + push

  • Conventional Commit prefix (feat:, fix:, perf:, chore:, refactor:).
  • Body explains why. Mention schema bumps (INDEX_SCHEMA_VER / blob format) and added dependencies.
  • Co-author trailer per repo convention.
  • Push directly to main is approved for the active iteration loop; PRs only when explicitly requested.

When something fails

  • typos: fix the misspelling; prefer the dictionary correction unless it's a proper noun.
  • markdownlint MD013 (line length > 120): split the line; for table cells, shorten the cell or move details to a code block under the table.
  • cargo-deny license rejection: add the SPDX expression to deny.toml's licenses.allow only if the license is genuinely permissive (Apache, MIT family, ISC, 0BSD, BSL, Unicode). Anything copyleft (GPL family) — escalate.
  • rust-max-lines: extract a submodule or helper file. Do not raise the cap.

Read the full file on GitHub · 53 lines

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.

  1. 8d ago First seen · 53 lines · 7 tokens per session scan A c4ff618f48f0

Subscribe to this mod's changes

poly-and-release-workflow is a skill published in the GitHub repository Goldziher/basemind (99 stars, last pushed 6d ago), licensed MIT. It adds 7 tokens to every session and 583 once invoked, about $0.0000 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-30.

Related

Other skills, from other repositories

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.

react/react · 42 tokens

sem

Use sem to get entity-level (function/class/method) semantic diffs, impact analysis, blame, and dependency context from any Git repo. Trigger this skill whenever the user asks what changed in a commit or PR, wants to understand the blast radius of a change, needs to know who last modified a function, wants to trace…

Ataraxy-Labs/sem · 112 tokens

sem

Semantic version control CLI. Entity-level diffs for Git (functions, classes, methods instead of lines).

Ataraxy-Labs/sem · 0 tokens

commit

Auto-fix, lint, test, and commit changes with a conventional commit message.

phel-lang/phel-lang · 16 tokens

vhs-e2e-gif

Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…

dimetron/pi-go · 106 tokens

056-design-avoid-breaking-changes

Use when you need to review a plan, OpenSpec change, specification, or implementation proposal for breaking-change risk across commands, skills, generated outputs, XML sources, README/docs, tests, CI, APIs, schemas, configuration, data, migration, and release guidance. This should trigger for requests such as Review…

jabrena/plinth · 106 tokens