release-sweep SKILL.md skillB
release-sweep from philoserf/claude-code-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add philoserf/claude-code-config/release-sweep@git:20261030.5a5a348Pins git:20261030.5a5a348 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- philoserf/claude-code-config
- Path
skills/release-sweep/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261030.5a5a348, committed Oct 30, 2026
- First version recorded
- Oct 26, 2026
- Size
- 4,646 bytes
- Repository stars
- 13
- License
- MIT
Cuts the releases that are ready across the philoserf repos, one background agent per repo, after one up-front confirmation of the list. Use when asked to cut, ship or release what is ready, or after /milestone-sweep leaves repos ready to release. Tags and GitHub releases are public, so the list is confirmed once before anything ships.
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 sweep The shipping half of `/milestone-sweep`. Separate on purpose: the sweep stops before shipping, and a release is a public step the user takes on purpose. One `repo-releaser` agent per repo cuts its release with `release-ship`. You find what is ready, get the list confirmed once, launch the agents, and clean up afterwards. **Run it on `almanac`, from a session started in `~/source/philoserf`**, for the same reasons as `/milestone-sweep`. ## 1. Find what is ready ```bash cd ~/source/philoserf && task sync ``` Stop if `sync` reports a repo as diverged or errored. With arguments, consider only those repos; `repo@version` fixes the version. Otherwise, a repo is a candidate when: - `release-check.sh` exits 3 with 0 FAIL and 0 WARN, - its `Changes since last tag` row shows at least one commit, and - it is not one of the unversioned sites named in `~/source/philoserf/CLAUDE.md`, which release by deploying, not tagging. Skip `obsidian-vault-changelog`, which `CLAUDE.md` excludes from all workspace work. **Propose a version for each candidate.** - **An open milestone named for a version:** use that. …
Read the whole file at its exact version.
How to install
mdr add philoserf/claude-code-config/release-sweep@sha256:f275e201863c8d52The line at the top of this page pins the label git:20261030.5a5a348, 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_dx5hvrvo75kezrsw)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 26, 2026 and Oct 30, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261030.5a5a348 latest | 2026-10-30 | 5a5a348 | 4,646 B | B | view · diff |
| git:20261026.7b9ba83 | 2026-10-26 | 7b9ba83 | 4,368 B | B | view · diff |
| git:20261026.8111bac | 2026-10-26 | 8111bac | 4,362 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4646 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
philoserf/claude-code-config · 13 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dx5hvrvo75kezrsw GET https://markdownregistry.com/api/v1/resolve?ref=philoserf/claude-code-config/release-sweep GET https://markdownregistry.com/api/v1/blob/f275e201863c8d5253fd4be79f0efb01147ee55c6cdc1938b8dd98b3a092928e
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.