📝 Add release skill #117

Merged
mat merged 2 commits from add-release-skill into main 2026-10-20 13:30:22 +00:00
Owner

Summary

.agents/skills/release/
└── SKILL.md — project-local release instructions for agents
inspect local / Forgejo / GitHub main and changes since the last release
  → propose version and notes plan; wait for approval before ANY push
  → reconcile fast-forward only; isolate the release in a worktree
  → manifest version-only commit → Forgejo main → Forgejo tag
  → verify or publish the same commit and tag on GitHub
  → GitHub release with generated notes and an explicit previous tag
  → verify publication and report synchronization

GitHub-generated notes keep the default What's Changed / New Contributors (when applicable) / Full Changelog format. If there are no generated change entries despite direct commits, the fallback preserves that format and the compare link rather than using a one-line summary.

Evidence

  • Before: no project-local release skill; the release flow and commit convention had to be explained interactively.
    After: one discoverable Agent Skills document specifies the full flow and the approval gate, including pre-sync pushes.
  • Frontmatter validated; all nine Bash examples pass bash -n.
  • Checked approval-before-push, worktree isolation, Forgejo commit/tag order, --verify-tag, generated notes with the previous tag, and changelog-preserving fallback.
  • git diff --check passes; only one new Markdown file, 112 added lines (below the 300-line limit).
  • python -m pytest -o addopts= -q in the isolated worktree: 136 passed.

Merge Danger

Door: two-way — remove the skill to revert this documentation change.

Blast Radius: agent release workflow. No integration runtime code changes. Following the skill performs real remote mutations, so it requires approval before any push and stops on divergence, conflicting tags, or unexpected refs.

## Summary ```text .agents/skills/release/ └── SKILL.md — project-local release instructions for agents ``` ```text inspect local / Forgejo / GitHub main and changes since the last release → propose version and notes plan; wait for approval before ANY push → reconcile fast-forward only; isolate the release in a worktree → manifest version-only commit → Forgejo main → Forgejo tag → verify or publish the same commit and tag on GitHub → GitHub release with generated notes and an explicit previous tag → verify publication and report synchronization ``` GitHub-generated notes keep the default What's Changed / New Contributors (when applicable) / Full Changelog format. If there are no generated change entries despite direct commits, the fallback preserves that format and the compare link rather than using a one-line summary. ## Evidence - **Before:** no project-local release skill; the release flow and commit convention had to be explained interactively. **After:** one discoverable Agent Skills document specifies the full flow and the approval gate, including pre-sync pushes. - Frontmatter validated; all nine Bash examples pass `bash -n`. - Checked approval-before-push, worktree isolation, Forgejo commit/tag order, `--verify-tag`, generated notes with the previous tag, and changelog-preserving fallback. - `git diff --check` passes; only one new Markdown file, 112 added lines (below the 300-line limit). - `python -m pytest -o addopts= -q` in the isolated worktree: **136 passed**. ## Merge Danger **Door:** two-way — remove the skill to revert this documentation change. **Blast Radius:** agent release workflow. No integration runtime code changes. Following the skill performs real remote mutations, so it requires approval before any push and stops on divergence, conflicting tags, or unexpected refs.
📝 Add release skill
All checks were successful
Validate / lint-ruff (push) Successful in 7s
Validate / test-pytest (push) Successful in 3m16s
Validate / type-check-mypy (push) Successful in 3m5s
706d71fb69
📝 Tighten release approval and verification
All checks were successful
Validate / lint-ruff (pull_request) Successful in 7s
Validate / test-pytest (pull_request) Successful in 3m17s
Validate / type-check-mypy (pull_request) Successful in 3m5s
Validate / lint-ruff (push) Successful in 8s
Validate / test-pytest (push) Successful in 3m16s
Validate / type-check-mypy (push) Successful in 3m4s
a41b17bc1d
mat changed title from WIP: 📝 Add release skill to 📝 Add release skill 2026-10-20 13:30:06 +00:00
mat merged commit bccec1369d into main 2026-10-20 13:30:22 +00:00
mat deleted branch add-release-skill 2026-10-20 13:30:23 +00:00
mat referenced this pull request from a commit 2026-10-20 13:30:23 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
mat/homeassistant-comwatt!117
No description provided.