docs: drop the SKILL.md pointer to the unshipped command file#35
Conversation
plugin.json declares only "skills": ["./skills/retro"], so commands/retro.md never reaches an installed skill: the deployed directory holds SKILL.md, checkpoints.yaml, evals, references and scripts. Every other path in SKILL.md is skill-relative, so the reader follows this one to a file that is not there. The pointer is also redundant. SKILL.md carries its own pipeline section, and references/workflow.md has the shared pipeline, so nothing an installed agent needs is behind that path. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the documentation in 'skills/retro/SKILL.md' by consolidating the details for the modes and the shared pipeline into 'references/workflow.md', removing the reference to 'commands/retro.md'. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Came from /retro: yes
Friction
Running
/retrofrom an installed skill,SKILL.md:24-25sent me tocommands/retro.mdfor the "full pipeline + commands". That file is not in the installed skill directory.Diagnosis
The file is not missing from the repo — it's never packaged.
plugin.jsondeclares only:so the deployed directory holds
SKILL.md,checkpoints.yaml,evals/,references/andscripts/— nocommands/. Verified: noretro.mdcommand file anywhere under~/.agents/or~/.claude/plugins/. Every other path inSKILL.mdis skill-relative (references/…), so this one reads as skill-relative too and dead-ends.Change
Drop the pointer. It's redundant:
SKILL.mdcarries its own "Pipeline (all modes)" section, andreferences/workflow.mdhas the shared pipeline under "Shared pipeline" — nothing an installed agent needs sits behind that path. Verified all 8 remainingreferences/…paths resolve from the installed skill dir.For the maintainer — the question I didn't decide
commands/retro.mdis 282 lines with per-phase detail that is richer thanreferences/workflow.md's pipeline section. This PR only stops the installed skill pointing at thin air; it does not resolve whether that content should ship (addcommands/to the plugin manifest?) or whether the duplication between the two files should collapse. That's your call, and I'd rather raise it than silently pick.Pre-commit hooks pass, including skill-repo structure validation and version parity.