tools: install and drive profullstack/cli-tools - #429
Merged
Conversation
Adds cli-tools to the workflow tools moshcode can install and pass through, so `moshcode install cli-tools` puts blog-post, domainfree, domainjson, gh-prs, gh-prs-merge, gh-prs-fix-all and tcfeed on PATH in one step, and `/cli-tools …` reaches them from the pit. The entry is shaped a little differently from its neighbours because the tool is a *set* of commands rather than one binary. `bin` probes the `cli-tools` dispatcher rather than any of the commands it installs: several of those names (gh-prs, tcfeed) may already exist from an older hand-rolled checkout, so probing one of them would report the set installed when it is not. binDirs covers ~/.local/bin for the same reason turso, gradient and kimi need it — the installer symlinks there and appends nothing to PATH, so the shell that ran the install cannot see the result. `upgrade` is the tool's own updater rather than a re-run of the installer. Re-running the installer would be wrong here: `cli-tools update` pulls and relinks the checkout that actually owns the commands, wherever it lives, and refuses to move a dirty or diverged tree rather than discarding work. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ThreatCrush Security Scan0 finding(s) in the 2 file(s) this pull request changes. Nothing in the files this pull request changes. 55 pre-existing finding(s) elsewhere in the repository — **HIGH/CRITICAL**: 5 | **MEDIUM**: 44 | **LOW**: 6Not introduced by this pull request. The full set is in the Security tab.
…and 35 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
Merged
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.
Adds
cli-toolsto the workflow tools moshcode can install and pass through, now that profullstack/cli-tools is public.moshcode install cli-tools # then /cli-tools list, /cli-tools updateOne step puts
blog-post,domainfree,domainjson,gh-prs,gh-prs-merge,gh-prs-fix-allandtcfeedon PATH, and/cli-tools …reaches them from the pit.Why this entry is shaped differently
The tool is a set of commands, not one binary, which changes three of the fields:
binprobes thecli-toolsdispatcher, not any of the commands it installs. Several of those names (gh-prs,tcfeed) may already exist from an older hand-rolled checkout, so probing one of them would report the set installed when it is not.binDirscovers~/.local/binfor the same reason turso, gradient and kimi need it: the installer symlinks there and appends nothing to PATH, so the shell that ran the install cannot see the result.upgradeis the tool's own updater, not a re-run of the installer. Re-running the installer would be wrong here —cli-tools updatepulls and relinks the checkout that actually owns the commands, wherever it lives, and refuses to move a dirty or diverged tree rather than discarding work.Checks
node --test test/tools.test.mjs— 32/32 pass, including a new case asserting the four points above and the existing install-script table extended with cli-tools.Also ran the suites that enumerate TOOLS (
completion,help,tui,upgrade,escalate-prime,completion-uninstall,upgrade-install-missing,upgrade-prime-sudo): 133 pass, 1 skipped, 0 fail.Installer verified end to end from the public URL into a sandbox: links all 8 commands, re-run is idempotent.
🤖 Generated with Claude Code