@staff0rd/assist 0.137.0 → 0.139.0

package/README.md

@@ -45,6 +45,8 @@ After installation, the `assist` command will be available globally. You can als
 - `/journal` - Append a journal entry summarising recent work, decisions, and notable observations
 - `/standup` - Summarise recent journal entries as a standup update
 - `/sync` - Sync commands and settings to ~/.claude
+- `/test-cover` - Incrementally increase test coverage by identifying and testing uncovered files
+- `/test-review` - Review existing tests for quality, coverage gaps, and adherence to conventions
 - `/inspect` - Run .NET code inspections on changed files
 - `/screenshot` - Capture a screenshot of a running application window
 - `/seq` - Query Seq logs from a URL or filter expression

package/claude/CLAUDE.md

@@ -5,7 +5,9 @@ The tool is invoked using the `assist` command and is installed globally. Use it
 When renaming TypeScript files or symbols, use the refactor commands instead of doing it manually:
 - `assist refactor rename file <source> <destination>` — rename/move a file and update all imports
 - `assist refactor rename symbol <file> <oldName> <newName>` — rename a variable, function, class, or type across the project
-Both default to dry-run; add `--apply` to execute.
+- `assist refactor extract <file> <functionName> <destination>` — extract a function and its private dependencies to a new file
+All default to dry-run; add `--apply` to execute.
+When using extract, name the destination file after the exported function (e.g. `updateWorkerCapacity.ts` for `updateWorkerCapacity`) to satisfy `useFilenamingConvention` lint rules.
 
 When the user mentions a Jira issue key (e.g. `BAD-671`, `PROJ-123`), use these commands to fetch context:
 - `assist jira view <issue-key>` — print the title and description

package/claude/commands/commit.md

@@ -15,3 +15,4 @@ Where:
 - Any subsequent arguments are paths to git add before committing
 - The commit message is 40 characters or less
 - The commit message does not reference Claude
+- Match the repo's commit message style (check git log). If the repo uses conventional commits, ensure the prefix accurately reflects the nature of the change (e.g. don't use `feat:` for non-functional changes like backlog updates or config)