principle-release-engineering SKILL.md skillA
principle-release-engineering from lugassawan/swe-workbench is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lugassawan/swe-workbench/principle-release-engineering@git:20260828.71a6399Pins git:20260828.71a6399 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lugassawan/swe-workbench
- Path
skills/principle-release-engineering/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260828.71a6399, committed Aug 28, 2026
- First version recorded
- May 20, 2026
- Size
- 6,926 bytes
- Repository stars
- 3
- License
- MIT
Release engineering — semver discipline, rollout strategy, rollback planning, expand-contract for breaking changes, kill-switch, idempotent release automation, post-release verification. Auto-load when cutting a release, planning a breaking API change, writing release notes, choosing a version bump, using a feature flag as a kill-switch, or building release automation scripts.
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
<!-- preload-canary: SWB-PRELOAD-PRINCIPLE-RELEASE-ENGINEERING --> # Release Engineering A release is a promise: a specific artifact, at a specific version, reachable at a specific address, forever. Every discipline here protects that promise. ## Semver discipline `MAJOR.MINOR.PATCH` — each level communicates an intent to callers. | Bump | Meaning | Example | |------|---------|---------| | PATCH | Backward-compatible bug fix only | `1.2.3 → 1.2.4` | | MINOR | New capability, backward-compatible | `1.2.3 → 1.3.0` | | MAJOR | Breaking change — callers must adapt | `1.2.3 → 2.0.0` | Never skip levels to signal "importance" (`1.0.0 → 3.0.0`). Pre-1.0 (`0.x.y`) still communicates intent: MINOR adds capability, PATCH fixes bugs, and a MAJOR bump to `1.0.0` signals API stability. If you're unsure between MINOR and MAJOR, default to MAJOR — over-caution is safe, under-caution breaks callers. ## Expand-contract for breaking changes Never atomically break a public contract. Ship in three independent deployments: 1. **Expand** — add the new interface alongside the old one. Both work. 2. **Migrate** — update all callers to the new interface. Old interface idle. …
Read the whole file at its exact version.
How to install
mdr add lugassawan/swe-workbench/principle-release-engineering@sha256:2f9ce045745e5f68The line at the top of this page pins the label git:20260828.71a6399, 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_45zt53iddtrn77a5)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 20, 2026 and Aug 28, 2026, about one every 25 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260828.71a6399 latest | 2026-08-28 | 71a6399 | 6,926 B | A | view · diff |
| git:20260820.16e7f08 | 2026-08-20 | 16e7f08 | 7,005 B | A | view · diff |
| git:20260811.925e30f | 2026-08-11 | 925e30f | 7,002 B | A | view · diff |
| git:20260725.074b496 | 2026-07-25 | 074b496 | 6,988 B | A | view · diff |
| git:20260520.fd66cab | 2026-05-20 | fd66cab | 6,921 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 (6926 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
lugassawan/swe-workbench · 3 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_45zt53iddtrn77a5 GET https://markdownregistry.com/api/v1/resolve?ref=lugassawan/swe-workbench/principle-release-engineering GET https://markdownregistry.com/api/v1/blob/2f9ce045745e5f6807028d056c99128d2f66568d1c6fb596059b6a80fb11335e
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.