@staff0rd/assist 0.393.0 → 0.395.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 +4 -3
- package/dist/commands/sessions/web/bundle.js +86 -86
- package/dist/index.js +380 -208
- package/package.json +2 -1
- package/pi/permission-gate.ts +46 -0
- package/pi/status-driver.ts +22 -0
package/README.md
CHANGED
|
@@ -93,7 +93,7 @@ After installation, the `assist` command will be available globally. You can als
|
|
|
93
93
|
- `assist init` - Initialize project with VS Code and verify configurations
|
|
94
94
|
- `assist new vite` - Initialize a new Vite React TypeScript project
|
|
95
95
|
- `assist new cli` - Initialize a new tsup CLI project
|
|
96
|
-
- `assist sync` - Copy command files to `~/.claude/commands`, sync `settings.json` and `CLAUDE.md`, and install the design assets — `claude/system-prompt.md` to `~/.claude/system-prompt.md` and `claude/skills/*` into `~/.claude/skills` (existing files in that directory are preserved). When the `codex` CLI is detected on PATH, additionally installs each command as a Codex skill at `~/.codex/skills/<name>/SKILL.md`, `CLAUDE.md` as `~/.codex/AGENTS.md`, and registers the `assist codex-hook` auto-approval hook (`PreToolUse` for `Bash`, plus `PermissionRequest`) in a managed block in `~/.codex/config.toml`, leaving the `~/.claude` copy untouched
|
|
96
|
+
- `assist sync` - Copy command files to `~/.claude/commands`, sync `settings.json` and `CLAUDE.md`, and install the design assets — `claude/system-prompt.md` to `~/.claude/system-prompt.md` and `claude/skills/*` into `~/.claude/skills` (existing files in that directory are preserved). When the `codex` CLI is detected on PATH, additionally installs each command as a Codex skill at `~/.codex/skills/<name>/SKILL.md`, `CLAUDE.md` as `~/.codex/AGENTS.md`, and registers the `assist codex-hook` auto-approval hook (`PreToolUse` for `Bash`, plus `PermissionRequest`) in a managed block in `~/.codex/config.toml`, leaving the `~/.claude` copy untouched. When the `pi` CLI is detected on PATH, additionally installs each command as a pi prompt template (native slash-command) at `~/.pi/agent/prompts/<name>.md`, `CLAUDE.md` as `~/.pi/agent/AGENTS.md`, and installs the assist pi extensions at `~/.pi/agent/extensions/assist-*.ts` — the `assist pi-hook` permission gate (reconciling pi's run-everything default with the shared allowlist) and the status driver (pushing running/waiting to the sessions daemon via `assist sessions set-status`) — leaving the `~/.claude` and `~/.codex` copies untouched
|
|
97
97
|
- `assist commit status` - Show git status and diff
|
|
98
98
|
- `assist commit <message>` - Commit staged changes with validation
|
|
99
99
|
- `assist commit <message> [files...]` - Stage files and create a git commit with validation
|
|
@@ -143,7 +143,7 @@ Backlog item ids are written and displayed in an `a`-prefixed form (e.g. item 55
|
|
|
143
143
|
- `assist backlog remove-phase <id> <phase>` - Remove a plan phase from a backlog item
|
|
144
144
|
- `assist backlog move-phase <id> <from> <to>` - Reorder a plan phase from one 1-based position to another, carrying its tasks and manual checks with it
|
|
145
145
|
- `assist backlog next [id] [--once]` - Pick and run the next backlog item, or open `/draft` if none remain; pass an `id` to run that item first, then continue chaining; `--once` exits after the first completed item run instead of prompting for another
|
|
146
|
-
- `assist backlog refine [id] [--once] [--harness <claude|codex>]` - Alias for `refine`
|
|
146
|
+
- `assist backlog refine [id] [--once] [--harness <claude|codex|pi>]` - Alias for `refine`
|
|
147
147
|
- `assist backlog start <id>` - Set a backlog item to in-progress
|
|
148
148
|
- `assist backlog stop` - Revert all in-progress backlog items to todo and reset their phase to 1
|
|
149
149
|
- `assist backlog done <id>` - Set a backlog item to done (blocked while any sub-task is not done)
|
|
@@ -206,6 +206,7 @@ Backlog item ids are written and displayed in an `a`-prefixed form (e.g. item 55
|
|
|
206
206
|
- `assist cli-hook deny add <pattern> <message>` - Add a deny rule for a command pattern
|
|
207
207
|
- `assist cli-hook deny remove <pattern>` - Remove a deny rule by pattern
|
|
208
208
|
- `assist codex-hook` - Codex `PreToolUse`/`PermissionRequest` hook that auto-approves read-only CLI commands, reading Codex's hook JSON from stdin and emitting Codex's decision shape. Reuses the same allowlist and deny logic as `cli-hook`; installed by `assist sync` when `codex` is on PATH
|
|
209
|
+
- `assist pi-hook` - pi permission-gate adapter that reads a `{ toolName, command }` tool-call descriptor from stdin and emits an `{ decision: "allow" | "deny" | "gate", reason }` JSON decision. Reuses the same allowlist and deny logic as `cli-hook`, so read-only commands auto-approve, deny-listed commands block, and everything else gates. Called by the `assist-permission-gate` pi extension that `assist sync` installs when `pi` is on PATH
|
|
209
210
|
- `assist edit-hook` - PreToolUse hook that blocks `Edit`/`Write`/`MultiEdit` calls from adding, changing, or removing a `// assist-maintainability-override` marker, or from introducing a code comment (use `code-comment set`/`confirm` for the rare comment that belongs)
|
|
210
211
|
- `assist code-comment set <file> <line> <text>` - Validate a single-line comment (max 50 chars; no block comments for `.ts`/`.js`) and issue a pin authorising its insertion; inserts `#` for `#`-comment files (`.yml`/`.yaml`, Dockerfile, `*.env`, `*.sh`) and `//` otherwise
|
|
211
212
|
- `assist code-comment confirm <pin>` - Insert the pinned comment at its file/line and clear the pin state
|
|
@@ -305,7 +306,7 @@ When iterating on assist itself: web server changes only need the `assist sessio
|
|
|
305
306
|
- `assist next [id] [--once]` - Alias for `backlog next [id]`; `--once` exits after the first completed item run instead of prompting for another
|
|
306
307
|
- `assist draft [description] [--once]` (alias: `feat`) - Launch Claude in `/draft` mode, chain into next on `/next` signal; an optional `description` is forwarded as `/draft <description>`; `--once` exits when the done signal arrives after the initial draft completes; `--resume-session <id>` resumes an interrupted Claude session (used by the sessions daemon when it restarts a running item)
|
|
307
308
|
- `assist bug [description] [--once]` - Launch Claude in `/bug` mode, chain into next on `/next` signal; an optional `description` is forwarded as `/bug <description>`; `--once` exits when the done signal arrives after the initial bug report completes; `--resume-session <id>` resumes an interrupted Claude session (used by the sessions daemon when it restarts a running item)
|
|
308
|
-
- `assist refine [id] [--once] [--harness <claude|codex>]` - Launch a coding harness in `/refine` mode to refine a backlog item; prompts for selection when no id given; `--once` exits when the done signal arrives after refinement completes; `--harness` picks the engine (`codex` runs `codex -C <cwd> <prompt>`), defaulting to the configured `harness.engine` (Claude); `--resume-session <id>` resumes an interrupted Claude session (used by the sessions daemon when it restarts a running item)
|
|
309
|
+
- `assist refine [id] [--once] [--harness <claude|codex|pi>]` - Launch a coding harness in `/refine` mode to refine a backlog item; prompts for selection when no id given; `--once` exits when the done signal arrives after refinement completes; `--harness` picks the engine (`codex` runs `codex -C <cwd> <prompt>`; `pi` runs `pi <prompt>` in the item's cwd), defaulting to the configured `harness.engine` (Claude); `--resume-session <id>` resumes an interrupted Claude session (used by the sessions daemon when it restarts a running item)
|
|
309
310
|
- `assist review-comments [number]` - Launch Claude in `/review-comments` mode to process PR review comments (single session, no chaining); when a PR number is supplied, checks out that PR via `gh pr checkout` first
|
|
310
311
|
- `assist signal next [id]` - Write a next signal to chain into `assist next`; when `id` is supplied, the parent launcher runs that backlog item directly
|
|
311
312
|
- `assist signal done [id]` - Write a done signal marking the session's initial task complete; an optional `id` surfaces the backlog item the session created onto its session card; `--once` launch sessions exit when it arrives, plain sessions ignore it
|