release v6.0.0: absorb release-flow into git-workflow, add merge-flow - #83
Merged
Merged
Conversation
…ate-changelog Dissolve `ceh-release-flow` into `ceh-git-workflow` and add `merge-flow`, the sibling that lands a branch without releasing it. `ceh-release-flow` was sequencing git skills and dispatching git subagents that all live in `ceh-git-workflow`; once a non-release flow joins it, the plugin name is false. Merging turns every cross-plugin reference into a local one. - Added `ceh-git-workflow:merge-flow` — changelog under `[Unreleased]` -> README -> commit -> PR -> merge -> cleanup, with no version bump, no tag, no release. It starts on the branch you are already on rather than cutting one; ten DECISION_LOG entries record `release-flow` step 2 being deviated from for exactly that reason. - Moved `release-flow` into `ceh-git-workflow`; deleted `direct-release-flow` and the `ceh-release-flow` plugin. - Moved `update-changelog` (and `scripts/check-semver.py`) from `ceh-documentation` to `ceh-git-workflow`. Every input it reads is git plumbing, so it fires on a git moment, not a documentation one. This is what keeps `ceh-git-workflow` at zero declared dependencies: the alternative was a `ceh-git-workflow` -> `ceh-documentation` edge, which breaks "a cross-cutting plugin may depend only on other cross-cutting plugins". `update-readme` stays put -- its call is conditional, so it remains prose. - Gave `update-changelog` an Unreleased mode, so an invoked run does not demand a version its caller forbids. - Stripped the "create a PR, merge it, delete the branch" claim from `open-pr` and `merge`; that phrase is `merge-flow`'s moment and both out-matched it. - Bundles: the three `-iterate` drop `ceh-release-flow`; `ceh-scenario-editorial` gains `ceh-git-workflow` so it keeps changelog capability. Breaking for existing installs: `/ceh-release-flow:release-flow` -> `/ceh-git-workflow:release-flow`, and `/ceh-documentation:update-changelog` -> `/ceh-git-workflow:update-changelog`. Versions: ceh-git-workflow 3.3.0, ceh-documentation 1.2.0, four bundles 1.1.0. Logged under CHANGELOG `[Unreleased]`; no repo tag (that is the release step). Decision record: DECISION_LOG Entry 85, PLUGIN_DEPENDENCY_PLAN D19. Validation: `validate.py` green; `check-semver.py CHANGELOG.md` green. Generated with [Claude Code](https://claude.com/claude-code) by CEH
Dissolves `ceh-release-flow` into `ceh-git-workflow` and ships `merge-flow`, the
flow that lands a finished branch without releasing it — changelog under
`[Unreleased]`, commit, PR, merge, no version bump and no tag. Absorbing the
release pipeline would have forced a `ceh-git-workflow` -> `ceh-documentation`
dependency, so `update-changelog` moved to `ceh-git-workflow` too; every input it
reads is git plumbing. `update-readme` stayed in `ceh-documentation`.
- Bump: MAJOR — a plugin is removed and two invoke paths break
(`/ceh-release-flow:release-flow` and `/ceh-documentation:update-changelog`).
Precedent: v5.0.0 was cut MAJOR for renaming one plugin and removing another.
- Manifests: ceh-git-workflow 3.2.9 -> 3.3.0, ceh-documentation 1.1.7 -> 1.2.0,
ceh-plan-build-review 1.1.5 -> 1.1.6, ceh-scenario-{service,library,webapp}-iterate
and ceh-scenario-editorial 1.0.0 -> 1.1.0; ceh-release-flow removed from
marketplace.json. All mirrored in .claude-plugin/marketplace.json.
- Docs: CHANGELOG `[Unreleased]` promoted to `[6.0.0]`. README.md and CLAUDE.md
were updated in 4b1a796 and need no further change. docs/CROSS_REFERENCES.md
and PLUGIN_DEPENDENCY_PLAN.md (D19) likewise.
Release content rides this feature branch rather than a fresh
`chore/release-v6.0.0` off main: the release *is* these changes, and a branch cut
from main would not contain them. Matches repo precedent (DECISION_LOG 509, 610,
707, 880, 911, 926, 1372, 1883, 1916).
Generated with [Claude Code](https://claude.com/claude-code) by CEH
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.
What
Dissolves the
ceh-release-flowplugin intoceh-git-workflow, addsmerge-flow, and movesupdate-changelog(withcheck-semver.py) fromceh-documentationtoceh-git-workflow. Cut asrepo tag v6.0.0.
ceh-release-flowplugin, includingdirect-release-flowrelease-flow->ceh-git-workflow;update-changelog+scripts/check-semver.py->ceh-git-workflowceh-git-workflow:merge-flow; an Unreleased mode inupdate-changelogopen-prandmergedescriptions; four scenario bundles;patch-built-versionhand-offWhy
ceh-release-flowsequencedceh-git-workflowskills and dispatchedceh-git-workflowsubagents.Its only original content was the ordering and the gates, and adding a flow that does not release
anything made the plugin name false.
merge-flowexists because the release pipeline answered a question most branches do not ask. Afinished branch still needs a changelog trace, a commit, a PR and a merge — folding that into
release-flowmeant bolting a bump onto work with nothing to release. It starts on the branch youare already on; ten
DECISION_LOGentries recordrelease-flow's fresh-branch step being deviatedfrom for exactly that reason.
update-changelogmoved because the merge would otherwise forceceh-git-workflow->ceh-documentation, breaking "a cross-cutting plugin may depend only on other cross-cuttingplugins". Every input that skill reads is git plumbing (
git describe --tags,git log,git tag,git remote), so it was a git moment filed under a topic label.ceh-git-workflowkeepszero declared dependencies.
update-readmedeliberately did not move: git appears in it once as one of two ways to see whatchanged, its gate asks about install steps and public API, both flows call it conditionally, and
ceh-seo:text-discoverabilityroutes to it as a sibling.How
update-readmecall in both flows is prose, not anInvoke the Skill toolinstruction —that is load-bearing, since
validate.pyrejects an invocation target outside a declareddependency.
update-changeloggained an Unreleased mode so an invoked run does not demand a version itscaller forbids.
open-prandmergeboth claimed "create a PR, merge it, delete the branch" — verbatimmerge-flow's moment, which they would have out-matched. Both now route it tomerge-flow.ceh-scenario-editorialgainsceh-git-workflowso it does not silently lose changelogcapability.
PLUGIN_DEPENDENCY_PLAN.mdsections 5-7 are left as the dated 2026-08-23 audit snapshot; section4 records D19 and says so.
Testing
python tools/validate-plugins/validate.py— green (28 plugins, manifests mirrored).python plugins/ceh-git-workflow/scripts/check-semver.py CHANGELOG.md— green from its newlocation, 76 versioned entries, none unreleased.
ceh-release-floworceh-documentation:update-changelogoutside thehistorical records (
CHANGELOG,DECISION_LOG, the dated audit sections).Breaking
Two invoke paths change for existing installs:
/ceh-release-flow:release-flow->/ceh-git-workflow:release-flow/ceh-documentation:update-changelog->/ceh-git-workflow:update-changelogDecision record:
DECISION_LOGEntry 85,PLUGIN_DEPENDENCY_PLAND19.Generated with Claude Code by CEH