shiplisted
Install: claude install-skill praisethebit/skills
Commit and push with the script `~/.claude/bin/ship`. Input:
$ARGUMENTS
1. Write the message:
- The subject follows the repo convention. If there is no convention, copy the style of `git log -5 --format=%s`.
- Add a body only for details. Write it in ASD-STE100 Simplified Technical English. Wrap at 72 characters.
- The subject names the change. Do not put an issue number in the subject: on a public repo, `#106` links to an unrelated GitHub issue.
- Do not add a `Co-Authored-By` line or other AI attribution. The README of each repo states the AI use.
2. From the repo root, run `~/.claude/bin/ship "<message>" -- <path>...` with only the changed paths. Set the Bash timeout to 600000: the hooks of a repo can take more than the default 2 minutes. For a path that you moved with `git mv` or removed with `git rm`, pass both the old path and the new path. The script stages and commits only those paths, pushes, and runs `git pull --rebase` one time if the remote is ahead.
3. If a pre-commit hook fails, fix the cause and run the script again. Never use `--no-verify`, `--force` or `git reset --hard`.
4. Tell the user the hash and subject. Tell the user about each file that the script lists as `not staged`.
5. The script exits 1 if a push fails. It prints `FAILED push of the code repo` or `FAILED push of the issue repo`. Tell the user which repo failed. A failed push in one repo does not undo the other.
6. If the script prints `pull --rebase failed`, fix the conflict with `g