publish-github-release SKILL.md skillA

publish-github-release from iampantherr/securecontext is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add iampantherr/securecontext/publish-github-release@v1.0.0

Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
iampantherr/securecontext
Path
examples/skills/publish-github-release/SKILL.md
Versions recorded
1
Latest version
v1.0.0, committed May 20, 2026
Size
6,673 bytes
Repository stars
8
License
MIT

Use this whenever the user asks to ship, publish, release, tag, or cut a new version of the project — OR when CHANGELOG.md has an "Unreleased" / in-progress section ready to be shipped. The skill bumps the version across all version-bearing files, regenerates the CHANGELOG entry from git log since the last tag, commits, pushes, waits for green CI, and creates a GitHub release with auto-generated notes.

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

# Publish a GitHub release

Generic procedure for shipping a new version of a project. Reads
project-specific config from `<project>/.publish-github-release-config.json`
if present (see `references/config-schema.md`).

## When to use

Trigger phrases (literal words the user might type):

- "ship v1.2.3"
- "release"
- "tag a new version"
- "publish"
- "cut a release"
- "make a new release"
- "bump version and release"
- "deploy this release to github"

Auto-detect trigger: if `CHANGELOG.md` has a `## [Unreleased]` heading with
entries underneath, and the agent has just finished a coherent unit of work,
suggest invoking this skill.

DO NOT use this for:

- Patch increments without code changes (use `npm version patch` directly).
- Pre-release / RC builds (use the `prerelease-tag` skill instead — coming
  in a later release).
- Repos with no GitHub remote (the skill assumes `gh` CLI auth and a remote
  named `origin` pointing at GitHub).

## Procedure

### Step 1 — Preflight gates

Run `scripts/preflight.py`. Reads project config; fails fast on:

- Working tree dirty (uncommitted changes)
- Branch is not on `main` (or whatever `config.main_branch` says)
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add iampantherr/securecontext/publish-github-release@sha256:0771028ae22e41c8

The line at the top of this page pins the label v1.0.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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_k2sk5noxwwmnvwne.svg)](https://markdownregistry.com/a/art_k2sk5noxwwmnvwne)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on May 20, 2026.

versioncommittedcommitsizeaudit
v1.0.0 latest2026-05-20 e940310 6,673 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (6673 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

GitHub

iampantherr/securecontext · 8 stars · license MIT · pushed 2026-10-07 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_k2sk5noxwwmnvwne
GET https://markdownregistry.com/api/v1/resolve?ref=iampantherr/securecontext/publish-github-release
GET https://markdownregistry.com/api/v1/blob/0771028ae22e41c8ab5495161cb9640d2a7de40476e6ca634434cdd7ad5aaadd

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 iampantherr/securecontext

CLAUDE.md CLAUDE.md file
iampantherr/securecontext · CLAUDE.md
git:20260503.537aa43 · audit A · 8 stars
writing-skills SKILL.md skill
iampantherr/securecontext · examples/skills/writing-skills/SKILL.md · Use this whenever the user asks to write, author, or scaffold a new SecureContext skill (Anthropic-style filesystem…
v1.0.0 · audit B · 8 stars
llms.txt llms.txt file
iampantherr/securecontext · llms.txt
git:20260503.537aa43 · audit A · 8 stars

Every file in iampantherr/securecontext

Browse by kind, by grade A, or by owner.