@staff0rd/assist 0.718.0 → 0.720.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -108,7 +108,7 @@ Every command supports `--help` for full detail on its flags and behaviour.
108
108
 
109
109
  ### Git and GitHub
110
110
 
111
- - `assist sync [--prune] [--force]` - Copy commands, settings and design assets to `~/.claude` (plus `~/.codex` and `~/.pi` when those CLIs are on PATH). No global instructions file is written any more — `~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md` and `~/.pi/agent/AGENTS.md` are all gone, and each harness instead receives the repo's composed advice at session start: Claude Code from the `assist advise --hook` SessionStart hook, Codex from `assist codex-hook` on its `SessionStart` event, and pi from the `assist-advice.ts` extension. Any of those three files an earlier sync left on disk is named on every run — sync never deletes them, since a hand-written one is indistinguishable from a leftover, but until they go they keep injecting the retired global instructions. With `--prune`, also lists commands in the target dirs that sync did not write — anything whose name is not in the repo's `claude/commands/*.md` set — and adding `--force` removes them. `~/.codex/skills` and `~/.pi/agent/prompts` are only inspected when those CLIs are detected; an orphaned codex skill directory is removed only when `SKILL.md` is its sole content, and any other is left in place with a reason. Subdirectories and non-`.md` files are listed separately and never removed. `--force` without `--prune` is an error
111
+ - `assist sync [--prune] [--force]` - Copy commands, settings and design assets to `~/.claude` (plus `~/.codex` and `~/.pi` when those CLIs are on PATH). A command whose frontmatter sets `skill: true` is written to `~/.claude/skills/<name>/SKILL.md` instead of `~/.claude/commands/<name>.md` (any old `commands/<name>.md` is deleted, and a symlinked `SKILL.md` is replaced rather than written through), so it takes precedence over a project skill of the same name; `/pr` opts in. No global instructions file is written any more — `~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md` and `~/.pi/agent/AGENTS.md` are all gone, and each harness instead receives the repo's composed advice at session start: Claude Code from the `assist advise --hook` SessionStart hook, Codex from `assist codex-hook` on its `SessionStart` event, and pi from the `assist-advice.ts` extension. Any of those three files an earlier sync left on disk is named on every run — sync never deletes them, since a hand-written one is indistinguishable from a leftover, but until they go they keep injecting the retired global instructions. With `--prune`, also lists commands in the target dirs that sync did not write — anything whose name is not in the repo's `claude/commands/*.md` set — and adding `--force` removes them. `~/.codex/skills` and `~/.pi/agent/prompts` are only inspected when those CLIs are detected; an orphaned codex skill directory is removed only when `SKILL.md` is its sole content, and any other is left in place with a reason. Subdirectories and non-`.md` files are listed separately and never removed. `--force` without `--prune` is an error
112
112
  - `assist activity [--since <date>]` - Chart GitHub commit activity per day (defaults to last 30 days)
113
113
  - `assist commit status` - Show git status and diff
114
114
  - `assist commit <message> [files...] [--ref <ref>]` - Stage files and create a git commit with validation. The message must be a single line under 50 characters; `--ref` is the only way to give the commit a body. Each `--ref` value is free text containing a URL (e.g. `--ref "rationale for removing it https://…"`) and becomes one `Ref:` trailer line, verbatim — commas are not separators, so repeat the flag to pass several. A value carrying no `http`/`https` URL is rejected before anything is staged
@@ -255,7 +255,7 @@ The Config tab of the sessions web dashboard never receives secret values: `GET
255
255
  - `assist refactor rename file <source> <destination>` - Rename/move a TypeScript file and update all imports (`--apply` to execute)
256
256
  - `assist refactor rename symbol <file> <oldName> <newName>` - Rename a symbol across the project (`--apply` to execute)
257
257
  - `assist refactor extract <file> <functionName> <destination>` - Extract a function and its private dependencies to a new file (`--apply` to execute)
258
- - `assist refactor restructure [root]` - Place every file under `root` (default `src`) by its import graph alone, so re-running on the result makes no moves. Roots (no importers in scope, or imported from outside) sit at `root`; a single-importer file nests in `<importer dir>/<importer basename>/`; a shared file sits directly in the lowest folder common to its importers; cycles stay together; tests sit next to their subject. Dry-run prints the moves, resulting tree, depth statistics and basename collisions. `--apply` moves the files, rewrites imports (including `import()`, `import("…")` types and `vi.mock` paths) and removes emptied folders; `--check` lists files that drift from the plan and exits non-zero. Files matching `restructure.ignore` globs are never moved. Modules named in `restructure.pin` (basename without extension) move up out of deep import chains into the folder of the nearest root or pinned module above them, taking their subtrees with them
258
+ - `assist refactor restructure [root]` - Place every file under `root` (default `src`) by its import graph alone, so re-running on the result makes no moves. Roots (no importers in scope, or imported from outside) sit at `root`; a single-importer file nests in `<importer dir>/<importer basename>/`; a shared file sits directly in the lowest folder common to its importers; cycles stay together; tests sit next to their subject. Dry-run prints the moves, resulting tree, depth statistics and basename collisions. `--apply` moves the files, rewrites imports (including `import()`, `import("…")` types and `vi.mock` paths) and removes emptied folders; `--check` lists files that drift from the plan and exits non-zero. Files matching `restructure.ignore` globs are never moved. Modules named in `restructure.pin` (basename without extension) move up out of deep import chains into the folder of the nearest root or pinned module above them, taking their subtrees with them. When the plan places files deeper than `restructure.maxDepth` (default 10), every mode lists the deep chains with the files beneath each folder and guidance for choosing feature-boundary pins, and `--check` exits non-zero
259
259
 
260
260
  ### Rules
261
261
 
@@ -1,5 +1,6 @@
1
1
  ---
2
2
  description: Raise a PR with a concise description
3
+ skill: true
3
4
  ---
4
5
 
5
6
  Run `assist prs raise --help` and follow its guidance exactly to compose and raise the pull request for the current branch. The help text is authoritative — it covers the section options, how to pitch each section, and whether to confirm the title and body in the terminal or leave that to the web UI. Do not use `gh pr create` directly.
@@ -4,6 +4,5 @@ description: Analyze and restructure tightly-coupled files
4
4
 
5
5
  1. Run `assist refactor restructure $ARGUMENTS` and review the planned moves, resulting tree and depth statistics.
6
6
  2. If it reports basename collisions or occupied targets, resolve them (rename one of the files with `assist refactor rename file`, or add a `restructure.ignore` glob) and re-run until there are no errors.
7
- 3. If the depth statistics show deep single-importer chains, add the module that heads each feature to `restructure.pin` in `assist.yml` so it moves up out of its chain, and re-run.
8
- 4. Run `assist refactor restructure --apply $ARGUMENTS`, then `assist refactor restructure --check $ARGUMENTS` to confirm the tree matches the plan.
9
- 5. Run `assist verify` and fix anything the moves broke.
7
+ 3. Run `assist refactor restructure --apply $ARGUMENTS`, then `assist refactor restructure --check $ARGUMENTS` to confirm the tree matches the plan.
8
+ 4. Run `assist verify` and fix anything the moves broke.