Files

Defame1297 591b9cccb8 fix(kyberforge): resolve second round of PR #91 review findings

Two review passes on PR #91 (correctness + simplification) found the
prior fixup commit (d6fd9b6) left the deprecation notice it added
half-applied, cited a nonexistent ADR, and introduced/compounded a
few duplicate restatements of the same facts across apm-workflow's
skill files and apm-orchestrate's Hard rules.

- plugin-author/SKILL.md cited ADR-0016 (doesn't exist) instead of
  ADR-0006 for the version-parity invariant.
- The deprecation banner on plugin-author/marketplace-author wasn't
  reflected in their routing `description:` frontmatter, forge's
  routing table, either kyberforge README skill table, or CONTEXT.md
  — now propagated consistently; routing behavior is unchanged since
  issue #90 (repo-wide apm conversion) hasn't landed yet.
- apm-orchestrate's `configure` operation only covered scaffolding a
  new package, not editing an existing apm.yml (e.g. removing a
  marketplace.packages[] entry, which has no dedicated `apm` CLI verb
  and is just a manifest edit). Added `edit-config`, intentionally
  ungated — a local file edit isn't the same class of irreversible
  action as `apm publish`, and normal review already gates the commit.
- Deduplicated facts restated 3-4x across SKILL.md/references/ADR
  boundaries (audit semantics, reserved name prefixes, marketplace-add
  direction, registries precondition), and trimmed configure.md's
  ~55-line apm.yml schema dump — copied near-verbatim from the
  research doc — down to a compact key list with a pointer, matching
  install.md's existing terse cross-referencing style.

Deliberately left as-is: apm-orchestrate's parallel/sequential
fan-out logic stays inline rather than extracted to a shared
reference, since neither git-orchestrate nor gitea-orchestrate need
it yet — premature extraction for a single caller.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0186ERbyACLRuRxPRnqwpa4m

2026-08-11 15:20:46 +00:00

references

fix(kyberforge): correct field classification and fill provenance gaps in plugin-author and marketplace-author

2026-06-28 11:09:13 +00:00

README.md

fix(marketplace-author): require version bump on every catalog mutation

2026-06-28 15:30:47 +00:00

SKILL.md

fix(kyberforge): resolve second round of PR #91 review findings

2026-08-11 15:20:46 +00:00

README.md

marketplace-author

Adds, removes, and updates plugin entries in the holocron marketplace manifest.

What it does

Manages entries in the plugins[] array of marketplace.json. Always updates both .claude-plugin/marketplace.json and .github/plugin/marketplace.json in the same edit pass — never one without the other. Routes automatically to add, remove, update, or create-from-scratch based on whether the files exist and whether the named plugin is already in the catalog. Bumps the catalog version on every mutation (minor for ADD/REMOVE, patch for UPDATE). Runs claude plugin validate . after every mutating operation.

Before you start

Have ready: the plugin name (kebab-case), what you want to do (add/remove/update), and — for add — the source type and source value. If adding from an external repo, know the source type (local path, GitHub, git URL, or npm).

Usage

/marketplace-author

No manual script. This skill is purely agentic — it reads, edits, and writes the marketplace files directly using the Read/Edit/Write tools.

Files

File	Purpose
`SKILL.md`	Skill instructions for agents
`references/manifest-fields.md`	Full field reference for top-level and per-entry `marketplace.json` fields, all four source type shapes with examples, and why both files must stay identical
`references/sources.md`	Research provenance — sources that informed this skill
`references/README.md`	Directory meta-documentation for references/

Marketplace files managed

File	Read by
`.claude-plugin/marketplace.json`	Claude Code
`.github/plugin/marketplace.json`	Copilot CLI