@staff0rd/assist 0.345.0 → 0.347.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 +5 -2
- package/allowed.cli-writes +1 -0
- package/dist/allowed.cli-writes +1 -0
- package/dist/commands/sessions/web/bundle.js +1 -1
- package/dist/index.js +467 -297
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -93,6 +93,7 @@ After installation, the `assist` command will be available globally. You can als
|
|
|
93
93
|
- `assist commit status` - Show git status and diff
|
|
94
94
|
- `assist commit <message>` - Commit staged changes with validation
|
|
95
95
|
- `assist commit <message> [files...]` - Stage files and create a git commit with validation
|
|
96
|
+
- `assist branch <slug> [--jira <key>]` - Create and switch to a new branch off the fresh remote default branch. Assembles the name as `[<prefix>/][<JIRA>-]<slug>` (prefix from the optional `branch.prefix` config, Jira key used verbatim), fetches and branches from `origin/<default>` (resolved dynamically, not hardcoded to main), and rejects slugs whose numeric tokens look like backlog IDs
|
|
96
97
|
- `assist prs` - List pull requests for the current repository
|
|
97
98
|
- `assist prs raise --title <title> --what <what> --why <why> [--how <how>] [--resolves <key>] [--force]` - Raise a pull request, assembling the body from `## What`, `## Why` (with `--resolves` Jira URLs appended inline), and an optional `## How`; errors if a PR already exists unless `--force` overwrites its title and body
|
|
98
99
|
- `assist prs edit [--title <title>] [--what <what>] [--why <why>] [--how <how>] [--resolves <key>]` - Update only the supplied sections of the current branch's pull request, preserving every other section of its body
|
|
@@ -168,7 +169,7 @@ The first backlog command in a repository that still has a local `.assist/backlo
|
|
|
168
169
|
- `assist verify --measure` - After the run, print a summary table of each command's status and duration (slowest first) plus a wall-clock total
|
|
169
170
|
- `assist verify init` - Add verify scripts to a project (writes to `assist.yml` by default; pass `--package-json` to write to `package.json` scripts instead)
|
|
170
171
|
- `assist verify hardcoded-colors` - Check for hardcoded hex colors in src/ (supports `hardcodedColors.ignore` globs in config)
|
|
171
|
-
- `assist verify block-comments` - Fail on any comment on a changed line (staged + unstaged), whether newly added or edited, reporting each offending file:line; functional machine directives are exempt and `blockComments.ignore` globs in config scope which files are scanned
|
|
172
|
+
- `assist verify block-comments` - Fail on any comment on a changed line (staged + unstaged), whether newly added or edited, reporting each offending file:line; functional machine directives are exempt and `blockComments.ignore` globs in config scope which files are scanned. Yaml `.yml`/`.yaml` files are scanned for `#` comments with no directive exemptions
|
|
172
173
|
- `assist verify forbidden-strings` - Check configured JSON files for disallowed values. Each `forbiddenStrings` rule names a `file`, a list of dot-`paths` to inspect (string or string[] values are scanned; other types skipped), and a `disallowed` wildcard matched via minimatch; any matching value fails the check. Zero rules is a no-op that passes
|
|
173
174
|
- `assist lint [-f, --fix]` - Run lint checks for conventions not enforced by oxlint (use `-f` to auto-fix)
|
|
174
175
|
- `assist lint init` - Initialize oxlint with baseline linter config
|
|
@@ -190,7 +191,7 @@ The first backlog command in a repository that still has a local `.assist/backlo
|
|
|
190
191
|
- `assist cli-hook deny add <pattern> <message>` - Add a deny rule for a command pattern
|
|
191
192
|
- `assist cli-hook deny remove <pattern>` - Remove a deny rule by pattern
|
|
192
193
|
- `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)
|
|
193
|
-
- `assist code-comment set <file> <line> <text>` - Validate a single-line comment (max 50 chars
|
|
194
|
+
- `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 `.yml`/`.yaml` files and `//` otherwise
|
|
194
195
|
- `assist code-comment confirm <pin>` - Insert the pinned comment at its file/line and clear the pin state
|
|
195
196
|
- `assist update` - Update assist to the latest version and sync commands
|
|
196
197
|
- `assist vscode init` - Add VS Code configuration files
|
|
@@ -295,6 +296,8 @@ When `commit.pull` is enabled in config, `assist draft`, `assist bug`, `assist r
|
|
|
295
296
|
|
|
296
297
|
When `commit.expectedBranch` is set (e.g. `main`), `assist commit` prints a prominent warning if HEAD is on any other branch before committing — so work committed (and pushed) on a stray branch in a repo that lands directly on the expected branch isn't silently orphaned. The warning is non-blocking: the commit still proceeds. With the key unset, behaviour is unchanged and no branch check runs.
|
|
297
298
|
|
|
299
|
+
When `branch.prefix` is set (e.g. `sw`), `assist branch <slug>` prepends `<prefix>/` to the branch name. With the key unset, no prefix segment is added.
|
|
300
|
+
|
|
298
301
|
## netcap browser extension
|
|
299
302
|
|
|
300
303
|
`assist netcap` only runs the receiver; the browser side is a raw Manifest V3 extension (no build step) under `netcap-extension/`. A MAIN-world content script patches `fetch`/`XMLHttpRequest` to capture `{url, method, status, requestBody, responseBody, timestamp}`, relays each entry to the background service worker (`window.postMessage` → `chrome.runtime.sendMessage`), and the background worker POSTs it to the receiver. The XHR patch reads the response across every `responseType` (`json`, `blob`, `arraybuffer`, `document`, not just `text`) — LinkedIn's voyager GraphQL calls use `responseType: "json"`, which exposes no `responseText`, so reading `responseText` alone captured those bodies empty. Forwarding happens in the background context, so the page's CSP (`connect-src`) never blocks it — the limitation that killed the earlier console-paste approach.
|
package/allowed.cli-writes
CHANGED