From 9f662807a13081c77e355349e4adc0927dec6544 Mon Sep 17 00:00:00 2001 From: Defame1297 Date: Sat, 4 Jul 2026 16:53:18 +0000 Subject: [PATCH] feat(forge): add version-bump orchestration via plugin-author subagent Step 4 ensures that after creating/updating artifacts in a plugin, forge invokes plugin-author (clean-context subagent) to bump the plugin version if not already done by other skills. Prevents missed version updates when artifacts are added to plugins. Co-Authored-By: Claude Haiku 4.5 --- plugins/kyberforge/skills/forge/SKILL.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/plugins/kyberforge/skills/forge/SKILL.md b/plugins/kyberforge/skills/forge/SKILL.md index 8d32819..ea2ea5b 100644 --- a/plugins/kyberforge/skills/forge/SKILL.md +++ b/plugins/kyberforge/skills/forge/SKILL.md @@ -60,3 +60,21 @@ State the classification and which skill(s) will run before invoking anything. If the clean audit surfaces any unresolved finding — not only a disagreement with the inline pass, any actionable finding on its own — loop: re-invoke the author skill (same fork-vs-inline judgment as the initial invocation) to resolve it, then re-run the clean audit again. Repeat until the clean audit comes back with nothing unresolved. Only then is the route done — the same resolve-before-close discipline `skill-author`/`agent-author` already apply to their own inline audit. When the intent spans multiple artifact types (e.g. a new skill inside a new plugin, then registering that plugin via `kyberforge:marketplace-author`), chain the routes in dependency order — an artifact that must exist on disk before another skill can target it goes first (e.g. `plugin-author` creates the plugin directory before `skill-author` scaffolds a skill inside it). + +## Step 4 — Bump plugin version (if applicable) + +After the routed skill finishes, check if the artifact was created or updated inside a plugin directory (any directory containing a `plugin.json`). + +**Skip this step if:** +- The artifact is standalone (not in any plugin) or scoped to user agent directories +- The author skill already bumped the plugin version (check the skill's audit output or completion message for version bump evidence) + +**If the artifact is in a plugin and no version bump was done:** + +Invoke `kyberforge:plugin-author` as a **clean-context subagent** (fresh, not forked) with this brief: + +> "The plugin at `` gained a new `` (``). Run the UPDATE flow to bump `version` in both manifests (Copilot and CC). Determine whether to bump minor (0.1.0) or patch (0.0.1) based on whether this is a new capability (minor) or a fix/refactor (patch). Do not release or tag — just update the manifests and commit." + +Use a clean-context subagent (not forked) so the version bump decision is made independently without anchoring to the earlier authoring context. This gives plugin-author a clear, isolated directive. + +Report completion to the user: "Updated `` version from X.Y.Z to X.Y.Z to reflect the new ``."