Rename skills to avoid collisions
Other skill sets use /review too? Rename yours.
The problem
Slash commands share a global namespace in most AI agents. If you have nanostack's /review and another tool's /review, the agent picks one and ignores the other. Which one wins depends on the agent, load order, and sometimes luck.
Rename during setup
During installation, use the --rename flag to prefix or rename any skill:
npx create-nanostack --rename review=nano-review npx create-nanostack --rename review=nano-review,qa=nano-qa
This creates the skill with the new name. The symlink points to the same skill file, but the agent sees it as /nano-review instead of /review.
You can also rename after installation:
npx create-nanostack rename review=nano-review
What gets renamed
The rename affects the trigger command only. Internally, the skill still identifies as its original name. Artifacts are saved under the original phase name. Sprint status shows the original name. This means:
- You type /nano-review to invoke it
- The artifact still saves to .nanostack/review/artifact.json
- sprint.sh status shows review: complete
- Other skills reference it by its original phase name
This separation keeps the internal plumbing stable while letting you control the external interface.
Persists across updates
Renames are stored in ~/.nanostack/renames.json:
{
"review": "nano-review",
"qa": "nano-qa"
}When you run npx create-nanostack update or /nano-update, the update process reads the rename config and re-applies the names. You do not need to rename again after updating.
List current names
npx create-nanostack --list Skills: /think → /think (default) /nano → /nano (default) /review → /nano-review (renamed) /qa → /nano-qa (renamed) /security → /security (default) /ship → /ship (default) /guard → /guard (default) /freeze → /freeze (default)
Reset to original
To undo all renames and go back to the default names:
npx create-nanostack rename --reset
To reset a specific skill:
npx create-nanostack rename review=review
Mapping a skill to its own original name removes the rename entry.
Rename custom skills too
The same mechanism works for custom skills. If you created a /deploy skill and it conflicts with another tool, rename it:
npx create-nanostack rename deploy=nano-deploy
Custom skill renames are stored in the same renames.json file alongside core skill renames.