@staff0rd/assist 0.301.0 → 0.302.1

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
@@ -160,7 +160,7 @@ The first backlog command in a repository that still has a local `.assist/backlo
160
160
  - `assist verify hardcoded-colors` - Check for hardcoded hex colors in src/ (supports `hardcodedColors.ignore` globs in config)
161
161
  - `assist verify comment-policy` - Flag comments added on changed lines (staged + unstaged) unless they carry a justification marker; supports `commentPolicy.markers` and `commentPolicy.ignore` globs in config
162
162
  - `assist lint [-f, --fix]` - Run lint checks for conventions not enforced by oxlint (use `-f` to auto-fix)
163
- - `assist lint init` - Initialize Biome with standard linter config
163
+ - `assist lint init` - Initialize oxlint with baseline linter config
164
164
  - `assist refactor check [pattern]` - Check for files that exceed the maximum line count
165
165
  - `assist refactor ignore <file>` - Add a file to the refactor ignore list
166
166
  - `assist refactor rename file <source> <destination>` - Rename/move a TypeScript file and update all imports (dry-run by default, use `--apply` to execute)
@@ -18,7 +18,7 @@ Run `assist run add --help` to see the current CLI usage and options. Use the ou
18
18
  Run `assist run add <name> <command> [args...]` with the appropriate arguments. For example:
19
19
 
20
20
  ```
21
- assist run add lint biome check --write
21
+ assist run add lint oxlint --fix
22
22
  ```
23
23
 
24
24
  If the command needs a working directory, use `--cwd <dir>`.
@@ -18,7 +18,7 @@ Run `assist run add --help` to see the current CLI usage and options. Use the ou
18
18
  `assist verify` runs every `verify:*` entry in parallel and only surfaces output for the ones that fail. A noisy success drowns the signal, so before registering the command, find the flag(s) that make the wrapped tool silent on success:
19
19
 
20
20
  - Check the tool's `--help` for options like `--silent`, `--quiet`, `-q`, `--reporter=dot`, `--reporter=line`, `--no-progress`, `--log-level=error`, `--no-color`, etc.
21
- - Prefer reporters that print only failures (e.g. `vitest --reporter=dot`, `eslint --quiet`, `tsc --pretty false`, `biome check --reporter=summary`).
21
+ - Prefer reporters that print only failures (e.g. `vitest --reporter=dot`, `oxlint --quiet`, `tsc --pretty false`).
22
22
  - If the tool always prints a banner or summary on success, look for a way to suppress it (redirect, `--no-summary`, etc.). Mention any unavoidable noise to the user.
23
23
 
24
24
  Apply those flags as part of the args you pass to `assist run add`.
@@ -29,7 +29,7 @@ Run `assist run add verify:<name> <command> [args...]` with the quiet flags appl
29
29
 
30
30
  ```
31
31
  assist run add verify:test vitest run --reporter=dot
32
- assist run add verify:lint eslint . --quiet
32
+ assist run add verify:lint oxlint . --quiet
33
33
  assist run add verify:types tsc --noEmit --pretty false
34
34
  ```
35
35