feat: Make prepare-release project-agnostic & GitHub-Release-aware (prepare-github-release)#28
Merged
Conversation
Rename prepare-release → prepare-github-release and refactor it into an ecosystem-agnostic orchestrator that detects the project type and analyzes GitHub workflows to choose the correct post-merge action. - Rename prompt (no backward-compat alias); aligns with the *-github-* convention since releases are GitHub-only (no Bitbucket equivalent) - Orchestrator detects WordPress plugin vs Node/npm and loads the matching partial; analyzes .github/workflows to decide bare-tag vs GitHub Release (fixes the wrong 'push the tag and it publishes' guidance for on: release:) - Add _partials/release-node.md and _partials/release-wordpress.md with the ecosystem-specific version source-of-truth, bump commands, and quality checks - Register both partials in PARTIALS and categorize them under react/wordpress in FILE_CATEGORIES.partials; rename in PROMPTS.workflow and FILE_CATEGORIES - Update README prompt/partial tables and CHANGELOG Closes #27 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Merged
miguelcolmenares
added a commit
that referenced
this pull request
Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Renames
prepare-release→prepare-github-releaseand refactors it into a project-agnostic, GitHub-Release-aware orchestrator. It auto-detects WordPress plugin vs Node/npm package and analyzes the repo's GitHub Actions workflows to choose the correct post-merge action (bare tag vs full Release).Motivated by the v2.5.0 release of this very repo, where the old WordPress-only prompt didn't apply to an npm package and gave wrong "push the tag and it publishes" guidance (
publish.ymltriggers onrelease: created).Related Issue
Closes #27
Changes Made
prepare-release.prompt.md→prepare-github-release.prompt.md(no alias). Releases are GitHub-only (Bitbucket has no Releases), so this aligns with the existing*-github-*convention.[Unreleased]→[X.Y.Z]; createsrelease/vX.Y.Zbranch + PR; analyzes.github/workflows/*.ymlto distinguish:on: release:→ must create a GitHub Releaseon: push: tags:→ pushing the tag is enough_partials/release-node.mdand_partials/release-wordpress.mdwith ecosystem-specific version source-of-truth, bump commands, and quality checks.PARTIALS; categorizedrelease-node→react,release-wordpress→wordpressinFILE_CATEGORIES.partials; prompt renamed inPROMPTS.workflowandFILE_CATEGORIES.prompts.Type of Change
prepare-release→prepare-github-release)Testing
node --test→ 44/44 passPROMPTS/PARTIALSmatch the filesystem; arrays alphabetically sorted; no staleprepare-releasereferences except the CHANGELOG rename note.Note on release ordering
This feature targets the next release (it's separate from the pending v2.5.0 bump in #26). Once #26 merges and 2.5.0 is published, this lands under a fresh
[Unreleased].🤖 Generated with Claude Code