chore: restore Node version check in publish skill - #172
Merged
Merged
Conversation
… wording runtime-agnostic Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
AGMASO
approved these changes
Jul 8, 2026
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
2 participants
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.
What
Two documentation fixes to the
publishskill, both flagged in review:Restore Node version verification (pre-flight). Commit
0cc16dfremoved thenvm usepre-flight step and its common-mistakes warning. The repo pins Node via.nvmrc(22.17.0) andengines(node: >=22), and there is no CI Node pin — so the skill was the only guardrail against publishing from a mismatched Node version. Restored as a version-manager-agnostic check (node --version, withnvm use/fnm useas examples) rather than hard-codingnvm.Make the task-tool instruction runtime-agnostic. The mandate hard-coded
TaskCreate. Reworded to reference "whatever task/todo tool your runtime provides (e.g.TaskCreate)" so the skill doesn't break if the checklist tool is named differently across runtimes.Why
No functional/code changes — skill markdown only.
🤖 Generated with Claude Code