Files
holocron/plugins/kyberforge/.apm/skills/instructions-author/references/verify.md
T
Defame1297andClaude Code d576695bb9 refactor(kyberforge): address #154 review and drop commit steps from author skills
- instructions-author: keep two Gotchas, move the rest to the Step 2 contract
  and verify.md; add references/content.md on what belongs in an instructions
  file and tighten the template bullets to match
- instructions-author, skill-author, agent-author: remove the commit
  verification step; committing is out of scope for author skills
- skill-author 1.0.6, agent-author 1.0.4 (ADR-0022 patch bumps)

Refs #148

Co-Authored-By: Claude Code <[email protected]>
Claude-Session: https://claude.ai/code/session_01KkT7RSDwDbmrM9T34b6sTi
2026-10-01 16:19:14 +00:00

1.7 KiB

source_keys
source_keys
apm-cli-0-28-0-experiments

Verifying a file in a throwaway package

Reached from SKILL.md Step 3. Run step 2 outside the repo: apm install writes apm_modules/, apm.lock.yaml and a rules directory, and install overwrites hand-authored rule files without warning.

  1. From the package root, a real compile. --validate always exits 0 and hides the missing-description, missing-applyTo and empty-body warnings, so it verifies nothing:

    apm compile --dry-run --target claude
    

    Resolve every warning it prints: missing description, missing applyTo, empty content, broken link, "Failed to parse".

  2. For a scoped rule, deploy it where nothing else can be overwritten:

    d=$(mktemp -d)
    printf 'name: scratch\nversion: 0.1.0\ntype: instructions\ntargets:\n  - claude\n' > "$d/apm.yml"
    mkdir -p "$d/.apm/instructions"
    cp <package-root>/.apm/instructions/<name>.instructions.md "$d/.apm/instructions/"
    (cd "$d" && apm install && cat .claude/rules/<name>.md)
    
  3. The deployed file must open with paths: listing the intended globs. No frontmatter block at all means applyTo was missing or did not parse: the rule would load in every session.

  4. Once rules sit in .claude/rules/, apm compile --target claude writes no CLAUDE.md and still exits 0, so an exit-code check proves nothing. To check the compiled root file instead, compile in that same clean directory before installing, or pass --force-instructions; after an install, --target claude writes nothing.

Delete the directory afterwards. Report only what was observed; Cursor's list-form globs and the Windsurf, Kiro and Antigravity runtimes stay unverified.