gh-oss-release SKILL.md skillA
gh-oss-release from jackchuka/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jackchuka/skills/gh-oss-release@git:20260604.0da3398Pins git:20260604.0da3398 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jackchuka/skills
- Path
gh-oss-release/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260604.0da3398, committed Jun 4, 2026
- First version recorded
- Mar 21, 2026
- Size
- 3,815 bytes
- Repository stars
- 15
- License
- MIT
Create GitHub releases across multiple OSS repositories. Checks release status via `gh oss-watch releases`, analyzes unreleased commits to recommend semver bumps, confirms with user, then creates releases. Triggers: "create releases", "release my packages", "check for releases", "oss releases", "gh oss-watch releases", "/oss-release", "release status", "bump versions".
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
# OSS Release
Batch release workflow for multiple OSS repositories using `gh oss-watch releases`.
## Workflow
### Step 1: Check Release Status
Run `gh oss-watch releases` to identify repos with unreleased commits.
If all repos are up to date, report that and stop.
### Step 2: Analyze Unreleased Commits
For each repo needing a release, fetch commit messages since the last tag in parallel:
```bash
gh api repos/<owner>/<repo>/compare/<last-tag>...HEAD --jq '[.commits[] | .commit.message | split("\n")[0]] | .[]'
```
### Step 3: Recommend Semver Bump
Classify each commit's first line and recommend the highest applicable bump:
| Commit pattern | Bump |
| ------------------------------------------------------- | --------- |
| `deps:`, `deps-dev:`, `ci:`, `chore:`, maintenance-only | **patch** |
| `feat:`, new functionality, non-breaking additions | **minor** |
| `BREAKING CHANGE`, `!:` suffix, API removals | **major** |
If ALL commits are deps/ci/chore, recommend **patch**. If any commit adds a feature, recommend **minor**. If any commit has breaking changes, recommend **major**.
…Read the whole file at its exact version.
How to install
mdr add jackchuka/skills/gh-oss-release@sha256:e0637b1a920777f6The line at the top of this page pins the label git:20260604.0da3398, 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_enkjiychptnhlei5)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 21, 2026 and Jun 4, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260604.0da3398 latest | 2026-06-04 | 0da3398 | 3,815 B | A | view · diff |
| git:20260512.0a51a44 | 2026-05-12 | 0a51a44 | 3,797 B | A | view · diff |
| git:20260421.19f33a5 | 2026-04-21 | 19f33a5 | 3,258 B | A | view · diff |
| git:20260408.efc937f | 2026-04-08 | efc937f | 3,245 B | A | view · diff |
| git:20260321.fb3b945 | 2026-03-21 | fb3b945 | 3,418 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 (3815 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
jackchuka/skills · 15 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_enkjiychptnhlei5 GET https://markdownregistry.com/api/v1/resolve?ref=jackchuka/skills/gh-oss-release GET https://markdownregistry.com/api/v1/blob/e0637b1a920777f6521088c10c51b998e11b4cf16ee16d03eee8a3b5344e303a
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.