fix: use /ship as the Desktop entry point - #1
Merged
Conversation
vadimsv1
marked this pull request as ready for review
July 24, 2026 22:40
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.
What changed
shipskill perform deterministic new-project setup itself/shipas the single Desktop/Cowork entry pointgo.mdonly as a backward-compatible Claude Code alias0.10.5/ship:goagainWhy
Runtime testing in Claude Desktop showed that
/ship:gois not available on that surface, while theshipskill is. The README and v0.10.4 release notes presented/ship:goas universal, so the public instructions were misleading.Claude Code namespaced skill behavior is called out separately (
/ship:shipmay appear there), while Desktop/Cowork users only need/ship.Validation
ship-doctor: ALL PASSEDship@ship-marketplacev0.10.5, enabled,errors: null