release-workflow SKILL.md skillA
release-workflow from savant0x/savant-code is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add savant0x/savant-code/release-workflow@v0.3.0Pins v0.3.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- savant0x/savant-code
- Path
.agents/skills/release-workflow/SKILL.md- Versions recorded
- 3
- Latest version
- v0.3.0, committed Oct 17, 2026
- First version recorded
- Jul 19, 2026
- Size
- 4,215 bytes
- Repository stars
- 11
- License
- Apache-2.0
Release cycle conventions for Savant-Code pipeline releases.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Release Workflow Standards (Savant-Code) ## When to Use <!-- Load this for all projects — defines the mandatory release cycle --> For any version bump, release, resume, or release-readiness check in Savant-Code. Releases flow exclusively through the public-release pipeline (`scripts/public-release.ts`; docs: `docs/public-release.md`). ## Procedure 1. **Open the version heading at bump time** — when the version bump lands (`bun run version:bump`), open `## <version> — <YYYY-MM-DD>` in `CHANGELOG.md` and write release notes directly beneath it as each change closes. **Never accumulate an `## Unreleased` section** — the release engine (`extractChangelogSection`) requires exactly one version heading matching the release version; Unreleased content never ships in notes. 2. **Audit phase before push** — run the gate battery and fix everything red: `bun run typecheck` (all workspaces), `bun run test`, `bun x eslint . --max-warnings 0`, `bun run lint:md`, `bun run validate:repository`, `bun run version:check`, plus the generated-doc drift checks (`generate:provider-docs:check`, `generate:protocol-bundle:check`). …
Read the whole file at its exact version.
How to install
mdr add savant0x/savant-code/release-workflow@sha256:2f5cae857fc4a4deThe line at the top of this page pins the label v0.3.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qzcrpw3cj2pxhuha)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 19, 2026 and Oct 17, 2026, about one every 45 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.3.0 latest | 2026-10-17 | bbffdc2 | 4,215 B | A | view · diff |
| v0.1.0 | 2026-10-12 | ac4bad2 | 1,900 B | A | view · diff |
| git:20260719.d6bc5a1 | 2026-07-19 | d6bc5a1 | 1,885 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4215 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
savant0x/savant-code · 11 stars · license Apache-2.0 · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qzcrpw3cj2pxhuha GET https://markdownregistry.com/api/v1/resolve?ref=savant0x/savant-code/release-workflow GET https://markdownregistry.com/api/v1/blob/2f5cae857fc4a4deb487f16cf6e11bbb8cdaeada7f7eb57637df4722cbf995a6
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from savant0x/savant-code
Every file in savant0x/savant-code