RIPDPI: Skill for Codex

RIPDPI Release Changelog

Build release notes from verifiable repository evidence. Treat commit subjects as leads, not proof of shipped behavior. Keep this skill read-only with respect to Git, GitHub, and release state.

Establish the exact range

1. Confirm the repository root, branch/worktree, and status.
2. Fetch tags when network access is available. Do not modify branches.
3. Resolve the base stable tag and target commit to immutable object IDs.
4. Require the base commit to be an ancestor of the target. Stop on a divergent range.
5. Record both IDs in every draft so later edits cannot silently change scope.

Use the latest stable tag that is an ancestor of the candidate as the base, unless the user explicitly selects another compatible stable tag. Use the immutable release-candidate SHA as the target; do not assume HEAD is still that candidate after a resume.

Generate the local evidence pack:

python3 .agents/skills/release-changelog/scripts/collect_release_changes.py \
  --base <base-tag> \
  --target <candidate-sha> \
  --output <temporary-directory>/vX.Y.Z-evidence.md

The script only reads Git data. It reports the exact range, commit taxonomy, changed components, diff totals, changelog candidates, and the complete commit inventory. Run without --base only when the latest reachable stable tag is the intended base.

Add GitHub context

When authenticated GitHub access is available, inspect rather than mutate:

gh release view <base-tag> --repo po4yka/RIPDPI --json tagName,name,publishedAt,body,assets
gh pr list --repo po4yka/RIPDPI --state merged --base main --limit 1000 \
  --json number,title,mergedAt,mergeCommit,labels,author,url

Keep only PRs whose mergeCommit.oid belongs to base..target, or whose squash commit can otherwise be proven to belong to the range. Do not include a PR merely because its merge date overlaps the release window. If GitHub data is partial or unavailable, state that gap and rely on the complete local commit inventory.