W Release

blockmatic/basilic-skills/skills/workflow/w-release

by blockmatic7e05e2abd052dc6b526e8a28e36d102d42bfd635No license1 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 6 days ago

Advisory review of release impact, changelog, and template contracts.

Instructions onlyDevOps & Cloud
AI-generated overview

Advisory review of release impact, changelog drafts, and template contracts before a release.

What it does
This skill performs an advisory-only review of a release or feature pull request. It diffs the branch against main or the previous version tag, lists affected payload paths, suggests a conventional title, and flags release-relevant commit types when payload paths changed. It also notes generator CLI, template include/exclude, and documentation snapshot impact, drafts user-facing changelog bullets with required adopter actions, and links tests, classification, and scaffold acceptance evidence. It explicitly does not bump versions, merge release PRs, or use publish credentials.
When to use it
Use it when preparing or reviewing a release PR or feature PR and you need an impact assessment, changelog draft, and template-contract check. It fits teams that keep release documentation and an authoritative changelog tool, and that require a human gate before proceeding.
Requirements
No scripts are shipped; it is instructions only. It needs read access to the repository, its release documentation, and git history or tags for diffing. It assumes a human gate and an authoritative release changelog process, and it must not use publish credentials.

Advisory only. Do not bump versions, merge a release PR, or use publish credentials. Read the repository's release docs first.

  1. Diff against main (feature PR) or the previous v* tag (release PR). List payload paths from those docs (Basilic example: apps/api|web|mobile, packages/, tools/, scripts/, .cursor/, .agents/, generator).
  2. Suggest a conventional title. Flag docs/chore/test/ci/style when payload paths changed unless the body has skip-release: true.
  3. Note generator CLI, template include/exclude, and docs snapshot impact. Generated trees must not gain the documentation app or the generator.
  4. Draft user-facing changelog bullets and required adopter actions. Keep the repo's release changelog authoritative (Basilic: Release Please).
  5. Link tests, classification, and (on a release PR) scaffold acceptance. Stop if a human gate is missing.

Source and attribution

Source:blockmatic/basilic-skillsinskills/workflow/w-releaseat commit7e05e2a

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal