Hi Matt,
Following up on the last comment in #483 (#483 (comment)), since #483 was about renaming and that's out of scope, but this part is a different problem and I think it's a small fix.
In the plugin, two skills call the review skill by its bare name:
implement/SKILL.md: Once done, call the Skill tool with "code-review" to review the work.
implement-spec/SKILL.md step 7: call the Skill tool with code-review on the integration branch.
In Claude Code (I'm on 2.1.292 with the 1.3.1 plugin), the bare name code-review is the built-in bug hunt review, while yours is only reachable as mattpocock-skills:code-review. So /implement can end with the built-in review instead of your Standards + Spec review, and the user can't fix it by typing the namespaced name, because the call comes from inside the skill. #809 hit the same thing and was closed as a duplicate of #483, and a few people in #483 reported /implement running the built-in one, or both.
Your answer in #483 was to call it by the namespaced name, so I think the skills should do the same. Something like:
-Once done, call the Skill tool with "code-review" to review the work.
+Once done, call the Skill tool with "code-review" from this pack (in the Claude Code plugin it's "mattpocock-skills:code-review", not the harness built-in) to review the work.
and the same in implement-spec step 7. No rename needed, and it still works for skills.sh installs.
Happy to open a PR if that helps.
Thanks!
Hi Matt,
Following up on the last comment in #483 (#483 (comment)), since #483 was about renaming and that's out of scope, but this part is a different problem and I think it's a small fix.
In the plugin, two skills call the review skill by its bare name:
implement/SKILL.md:Once done, call the Skill tool with "code-review" to review the work.implement-spec/SKILL.mdstep 7:call the Skill tool with code-review on the integration branch.In Claude Code (I'm on 2.1.292 with the 1.3.1 plugin), the bare name
code-reviewis the built-in bug hunt review, while yours is only reachable asmattpocock-skills:code-review. So/implementcan end with the built-in review instead of your Standards + Spec review, and the user can't fix it by typing the namespaced name, because the call comes from inside the skill. #809 hit the same thing and was closed as a duplicate of #483, and a few people in #483 reported/implementrunning the built-in one, or both.Your answer in #483 was to call it by the namespaced name, so I think the skills should do the same. Something like:
and the same in
implement-specstep 7. No rename needed, and it still works for skills.sh installs.Happy to open a PR if that helps.
Thanks!