Defame1297
a3e721e937
Why: ADR-0022 made `metadata.version` mandatory in SKILL.md frontmatter, but three documents still instructed the opposite — that `version:`, `source:`, `references:` and `when:` belong in a separate META.md. That recommendation was never implemented: META.md exists exactly once in this repo, inside a vendored third-party research example, and all 39 skills now contradict it. A stale instruction that outranks nothing is worse than no instruction, because an author following it undoes the ADR. Implementation notes: - Two LESSONS.md entries deleted outright — their entire payload was the rejected fix. Two kept and rewritten: the copy-fill entry loses only its META-TEMPLATE clause, and the `model:` entry keeps the provider-extension fact and the invocation-time boundary rule, which stand on their own. - One factual error corrected in passing: the `extracted` slug entry claimed provenance is recorded in META.md. It lives in `references/sources.md` keyed by `source_keys:`, verified against validate-provenance.sh. - Both docs/notes files gain `metadata.version` in their required-field lists. Deleting the stale paragraph while leaving those lists silent would have re-created the gap. - `bin/write-docs` carried `metadata.version: "1.0"` — the only non-semver value in the corpus, and the result of relocating its old top-level `version:` without normalising it. Now `1.0.0`. ADR-0022 records the relocation it previously omitted, which issue #127 had asked it to decide. Impact: patch bumps for the four plugins whose `.apm/` content changed — bin, git, gitea, kyberforge. core and lint are untouched and stay put. Root apm.yml's `executables.allow` key and marketplace package versions move in lockstep; the marketplace release version is unchanged. Refs: #127 ADR: 0022 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EeH8SCbcrCAQrtymkNuhKP
37 lines
894 B
YAML
37 lines
894 B
YAML
name: gitea
|
|
version: 1.3.8
|
|
description: Skills and agents for working with a Gitea forge through its HTTP API — the forge's own objects, as distinct from the local git clone.
|
|
author:
|
|
name: Defame1297
|
|
email: defame1297@rkdr.net
|
|
url: https://git.dev.rkdr.net/Defame1297/
|
|
license: MIT
|
|
homepage: https://git.dev.rkdr.net/Defame1297/holocron/src/branch/main/plugins/gitea
|
|
repository: https://git.dev.rkdr.net/Defame1297/holocron/src/branch/main/plugins/gitea
|
|
keywords:
|
|
- gitea
|
|
- issues
|
|
- prs
|
|
- milestones
|
|
- releases
|
|
- branches
|
|
|
|
# Constrains what .apm/ may contain: instructions, skill, hybrid, or prompts
|
|
type: hybrid
|
|
|
|
targets:
|
|
- claude
|
|
- copilot
|
|
- codex
|
|
|
|
# "auto" publishes the authoritative local source layout, or list explicit
|
|
# repo paths to define the complete publication set.
|
|
includes: auto
|
|
|
|
dependencies:
|
|
apm: []
|
|
mcp: []
|
|
devDependencies:
|
|
apm: []
|
|
scripts: {}
|