Part of #72 (Phase 6).
_meta.json written at skill install time, and PR/issue attribution updated to a pinned-SHA link instead of the current $SOURCE_REPO blob/main pointer.
Approach (we do not control DAM install internals)
Prefer Option 2: each skill's entry point checks for _meta.json at startup and writes it if absent, resolving the SHA via gh api repos/rossoctl/agent-skills/commits?path=skills/<name> --jq '.[0].sha'. No changes outside the skill. Promote to a repoman skill-init bootstrap (Option 1) only if first-run latency becomes noticeable.
Scope
- Skill entry points (Option 2) or
scripts/repoman-skill-init.sh (Option 1).
- Scanner/fixer scripts read
_meta.json and inject the SHA into PR/issue bodies.
Additive: existing SOURCE_REPO attribution continues until this lands.
Assisted-By: Claude Code
Part of #72 (Phase 6).
_meta.jsonwritten at skill install time, and PR/issue attribution updated to a pinned-SHA link instead of the current$SOURCE_REPOblob/main pointer.Approach (we do not control DAM install internals)
Prefer Option 2: each skill's entry point checks for
_meta.jsonat startup and writes it if absent, resolving the SHA viagh api repos/rossoctl/agent-skills/commits?path=skills/<name> --jq '.[0].sha'. No changes outside the skill. Promote to arepoman skill-initbootstrap (Option 1) only if first-run latency becomes noticeable.Scope
scripts/repoman-skill-init.sh(Option 1)._meta.jsonand inject the SHA into PR/issue bodies.Additive: existing
SOURCE_REPOattribution continues until this lands.Assisted-By: Claude Code