From sop-writer
Update revision date and version metadata across one or many SOPs in the current project, then optionally recompile. Reads the Typst frontmatter (or a leading metadata block) of each target document, increments the revision (semver-style: minor by default, patch/major on request), updates the date to today, and writes back. Use when the user has reviewed a set of procedures and wants to mark them as a fresh revision.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sop-writer:bump-revisionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bump revision metadata across one or more SOPs.
Bump revision metadata across one or more SOPs.
sops/*.typ)binders.yaml (bumps every doc in that binder)all — every .typ SOP in the project (confirm before doing this)patch (default — 1.0 → 1.0.1), minor (1.0 → 1.1), or major (1.0 → 2.0).compile on each affected doc and rebuild any binder that references it.all was requested or the list is large (>10 files).#let meta = (
title: "Rocket & Missile Alert Response",
revision: "1.2",
date: "2026-04-01",
audience: "household members",
source: "Home Front Command",
)
revision per the requested level.date to today's ISO date.revisions: history list exists, append (version: "<new>", date: "<today>", note: "<note>").compile for each updated .typ. If any of them belong to a binder defined in binders.yaml, also rebuild that binder.bump-revision."1.0", "2024.04", "r3". Prefer semver-ish but accept whatever's already there and increment numerically where possible. If unparseable, ask.npx claudepluginhub danielrosehill/claude-code-plugins --plugin sop-writerGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.