Skip to content
Back to skills

Obpis

ASecurity

- **Source ADR:** `docs/design/adr/foundation/ADR-0.0.15-ghi-driven-patch-release-ceremony/ADR-0.0.15-ghi-driven-patch-release-ceremony.md` - **Checklist Item:** #6 - "Ceremony skill: narrative drafting, RELEASE_NOTES, GitHub release"

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 11, 2026
testinggobashgit

Works with

  • cli

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned November 11, 2026

npx -y skills add tvproductions/gzkit --skill obpis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Obpis?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Obpis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tvproductions-obpis/badge)](https://www.skillsdirectory.com/skills/tvproductions-obpis)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: OBPI-0.0.15-05-ceremony-skill
parent: ADR-0.0.15-ghi-driven-patch-release-ceremony
item: 5
lane: Heavy
status: attested_completed
---

# OBPI-0.0.15-05: Patch Release Ceremony Skill

## ADR Item

- **Source ADR:** `docs/design/adr/foundation/ADR-0.0.15-ghi-driven-patch-release-ceremony/ADR-0.0.15-ghi-driven-patch-release-ceremony.md`
- **Checklist Item:** #6 - "Ceremony skill: narrative drafting, RELEASE_NOTES, GitHub release"

**Status:** Draft

## Objective

A `gz-patch-release` skill orchestrates the ceremony: the agent drafts narrative
release notes from qualifying GHIs, the operator approves, and the skill handles
RELEASE_NOTES.md update, git-sync, and GitHub release creation — mirroring the
closeout ceremony's Steps 9-10 pattern.

## Lane

**Heavy** - Operator-facing ceremony with RELEASE_NOTES and GitHub release
creation. Changes the operator workflow contract.

## Allowed Paths

- `.gzkit/skills/gz-patch-release/SKILL.md` (new)
- `.claude/skills/gz-patch-release/SKILL.md` (mirror)
- `RELEASE_NOTES.md`

## Denied Paths

- `src/gzkit/commands/patch_release.py` — CLI handled in prior OBPIs
- `src/gzkit/commands/closeout.py` — no modifications

## Requirements (FAIL-CLOSED)

1. REQUIREMENT: Skill MUST draft narrative release notes from GHI titles and
   descriptions — NEVER use raw GHI titles as release notes
2. REQUIREMENT: Operator MUST approve release notes before any publish action
3. REQUIREMENT: `uv run gz git-sync --apply --lint --test` MUST run immediately
   before `gh release create` — same policy as closeout ceremony
4. REQUIREMENT: Skill MUST apply the Iron Law pattern from gz-obpi-pipeline:
   once the operator approves, the skill flows through all remaining steps
   without pauses or summaries
5. REQUIREMENT: Foundation ADRs (0.0.x) MUST skip GitHub release creation per
   existing policy

> STOP-on-BLOCKERS: if the closeout ceremony skill is being refactored
> concurrently (GHI #65), coordinate to avoid conflicts.

## Discovery Checklist

**Governance (read once, cache):**

- [ ] `AGENTS.md` or `CLAUDE.md` - agent operating contract
- [ ] Parent ADR - understand full context

**Context:**

- [ ] Parent ADR: `docs/design/adr/foundation/ADR-0.0.15-ghi-driven-patch-release-ceremony/ADR-0.0.15-ghi-driven-patch-release-ceremony.md`
- [ ] OBPI-0.0.15-01 through OBPI-0.0.15-04 (prerequisites)
- [ ] Closeout ceremony skill: `.gzkit/skills/gz-adr-closeout-ceremony/SKILL.md`
- [ ] OBPI pipeline skill: `.claude/skills/gz-obpi-pipeline/SKILL.md`

**Prerequisites (check existence, STOP if missing):**

- [ ] `gz patch release` CLI command operational (from prior OBPIs)
- [ ] Closeout ceremony skill exists as pattern reference

**Existing Code (understand current state):**

- [ ] Closeout ceremony Steps 9-10: `.gzkit/skills/gz-adr-closeout-ceremony/SKILL.md`
- [ ] OBPI pipeline Iron Law: `.claude/skills/gz-obpi-pipeline/SKILL.md`

## Quality Gates

### Gate 1: ADR

- [ ] Intent and scope recorded in this OBPI brief
- [ ] Parent ADR checklist item quoted

### Gate 2: TDD

- [ ] Tests written before/with implementation
- [ ] Tests pass: `uv run gz test`
- [ ] Validation commands recorded in evidence with real outputs

### Code Quality

- [ ] Lint clean: `uv run gz lint`
- [ ] Type check clean: `uv run gz typecheck`

### Gate 3: Docs (Heavy)

- [ ] Docs build: `uv run mkdocs build --strict`
- [ ] Skill documented in runbook

### Gate 4: BDD (Heavy)

- [ ] N/A — skill is agent-orchestrated, not CLI-testable via behave

### Gate 5: Human (Heavy)

- [ ] Human attestation recorded

## Verification

```bash
uv run gz lint
uv run gz typecheck
uv run gz test
uv run mkdocs build --strict

# Specific verification — skill registration and structure
test -f .gzkit/skills/gz-patch-release/SKILL.md && echo "PASS: skill exists"
test -f .claude/skills/gz-patch-release/SKILL.md && echo "PASS: mirror exists"
grep -q "gz-patch-release" .gzkit/manifest.json && echo "PASS: registered in manifest"
uv run gz validate --surfaces
```

## Acceptance Criteria

- [ ] REQ-0.0.15-05-01: Skill drafts narrative release notes from GHI content
- [ ] REQ-0.0.15-05-02: Operator approval gate before publish
- [ ] REQ-0.0.15-05-03: git-sync immediately before GitHub release
- [ ] REQ-0.0.15-05-04: Iron Law pattern applied to post-approval steps
- [ ] REQ-0.0.15-05-05: Foundation ADRs skip GitHub release

## Completion Checklist

- [ ] **Gate 1 (ADR):** Intent recorded in brief
- [ ] **Gate 2 (TDD):** Tests pass, coverage maintained
- [ ] **Code Quality:** Lint, format, type checks clean
- [ ] **Value Narrative:** Problem-before vs capability-now is documented
- [ ] **Key Proof:** One concrete usage example is included
- [ ] **OBPI Acceptance:** Evidence recorded below

> For ceremony steps and lane-inheritance attestation rules, see `AGENTS.md` section `OBPI Acceptance Protocol`.

## Evidence

### Gate 1 (ADR)

- [x] Intent and scope recorded in OBPI brief and parent ADR checklist item #6

### Gate 2 (TDD)

```text
Ran 2690 tests in 20.736s — OK
All checks passed (lint, typecheck, tests, docs validation, surface validation, mkdocs build)
```

### Code Quality

```text
Lint: All checks passed
Typecheck: Passed (1 pre-existing warning in personas.py)
Surfaces: All validations passed
Documents: All validations passed
MkDocs: Built in 1.31s (strict mode)
```

### Value Narrative

Before this OBPI, gzkit had the `gz patch release` CLI command but no agent
ceremony skill to orchestrate the human-in-the-loop release workflow. An operator
asking for a patch release would get no structured guidance. Now, `gz-patch-release`
provides a deterministic ceremony with narrative drafting from GHI content, an
operator approval gate, Iron Law post-approval execution, and Foundation skip policy.

### Key Proof


test -f .gzkit/skills/gz-patch-release/SKILL.md && echo PASS: canonical skill exists
test -f .claude/skills/gz-patch-release/SKILL.md && echo PASS: mirror exists
uv run gz validate --surfaces => All validations passed

### Implementation Summary


- Files created: .gzkit/skills/gz-patch-release/SKILL.md (canonical skill, 232 lines)
- Files mirrored: .claude/skills/gz-patch-release/SKILL.md (via gz agent sync control-surfaces)
- Tests added: N/A (markdown skill artifact, verified via surface validation and mkdocs build)
- Date completed: 2026-04-08
- Attestation status: Completed
- Defects noted: Brief frontmatter id was short-form, fixed to match ledger slug

## Tracked Defects

_No defects tracked._

## Human Attestation

- Attestor: `g0`
- Attestation: attest completed
- Date: 2026-04-08

---

**Brief Status:** Completed

**Date Completed:** 2026-04-08

**Evidence Hash:** -

Files in this skill

  • OBPI-0.0.15-01-cli-command-scaffold.md5.7 KB
  • OBPI-0.0.15-02-ghi-discovery-cross-validation.md5.1 KB
  • OBPI-0.0.15-03-version-sync-integration.md5.5 KB
  • OBPI-0.0.15-04-dual-format-manifest.md4.9 KB
  • OBPI-0.0.15-05-ceremony-skill.md6.5 KB
  • OBPI-0.0.15-06-dogfood-fix-version-drift.md5.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in testing →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.