fix(skills): the repo's dogfood skill was invisible — renamed to apr-dogfood so it can actually be invoked - #2361
Merged
Merged
Conversation
…dogfood so it can actually be invoked `.claude/skills/dogfood/SKILL.md` had no `name:` in its frontmatter, so it took its name from the directory. That collides with a personal user-scope skill at `~/.claude/skills/dogfood/`, and on any machine where both exist the USER one wins: the repo's skill NEVER APPEARS in the session's skill listing at all. It cannot be invoked, and nothing warns (#2332). Confirmed live in this session: the `dogfood` skill offered to the agent is described as "Sovereign-stack PRE-RELEASE protocol ... (copia, forjar, pmat, trueno, aprender)" — the user-scope one. The repo's, "Dogfood apr-cli — rebuild, install, exercise all commands against real models", is absent. WHY THIS MATTERS MORE THAN A NAMING NIT: #2357 hardened this file's Gate 1 and Gate 13 because the release-certifying protocol was validating an unpinned, possibly 26-day-old binary. Those edits were made to a file that does not run. A shadowed skill is worse than a missing one — edits to it look effective and change nothing, which is the same failure mode as every other defect in the current andon sweep. Fix: `git mv` to `.claude/skills/apr-dogfood/` plus an EXPLICIT `name: apr-dogfood`. The explicit name is the durable half — a directory rename alone would silently re-collide the day someone adds `~/.claude/skills/apr-dogfood/`. The comment above it records why, so the next person does not "tidy" it away. Updated the four docs that pointed at the old path (README, apr-cli-qa-spec, claude-code-skills/README, the albor dogfood template) and the `/dogfood` invocation references. CHANGELOG entries are historical records and are left alone. NOT fixed here: the user-scope `~/.claude/skills/dogfood/` still exists and still wins the name `dogfood`. That is a file on a developer's machine, not a repo artifact — the repo's job is to stop colliding with it, which this does. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #2332.
.claude/skills/dogfood/SKILL.mdhad noname:in its frontmatter, so it took its name from the directory. That collides with a personal user-scope skill at~/.claude/skills/dogfood/, and on any machine where both exist the user one wins — the repo's skill never appears in the session's skill listing at all. It cannot be invoked, and nothing warns.Confirmed live in this session. The
dogfoodskill offered to the agent is described as "Sovereign-stack PRE-RELEASE protocol … (copia, forjar, pmat, trueno, aprender)" — the user-scope one. The repo's, "Dogfood apr-cli — rebuild, install, exercise all commands against real models", is absent.Why this matters more than a naming nit
#2357 hardened this file's Gate 1 and Gate 13, because the release-certifying protocol was validating an unpinned, possibly 26-day-old binary.
Those edits were made to a file that does not run.
A shadowed skill is worse than a missing one: edits to it look effective and change nothing. That is the same failure mode as every other defect in the current sweep — a surface that reports success while doing nothing.
Fix
git mvto.claude/skills/apr-dogfood/plus an explicitname: apr-dogfood.The explicit name is the durable half — a directory rename alone would silently re-collide the day someone adds
~/.claude/skills/apr-dogfood/. The comment above it records why, so the next person doesn't tidy it away.Updated the four docs pointing at the old path (README,
apr-cli-qa-spec,claude-code-skills/README, the albor dogfood template) and the/dogfoodinvocation references. CHANGELOG entries are historical records and left alone.Not fixed here
The user-scope
~/.claude/skills/dogfood/still exists and still owns the namedogfood. That's a file on a developer's machine, not a repo artifact — the repo's job is to stop colliding with it, which this does.🤖 Generated with Claude Code