nex-code 0.5.27 → 0.5.28

package/dist/skills/code-review.md

@@ -0,0 +1,39 @@
+# Code Review Skill
+<!-- trigger: code review, review code, review the, review these, review my, review this -->
+<!-- trigger: pull request, PR review, check the code, audit code -->
+<!-- trigger: code quality, code smell -->
+
+## Instructions
+
+When activated for code review, follow this tool sequence:
+
+1. **Scope the review** — identify which files were changed:
+   - Use `git_diff` to see staged or recent changes
+   - If reviewing a specific file, narrow with `read_file` on that file
+   - For multi-file changes, `grep` for key symbols to understand scope
+
+2. **Read the changes** — focus on the delta, not the whole file:
+   - Use `read_file` with `line_start`/`line_end` for targeted sections
+   - Prefer `git_diff` output over reading entire files
+   - Read only what changed plus relevant context lines
+
+3. **Check for common issues** (run these in parallel when possible):
+   - **Logic errors**: off-by-one, null/undefined access, incorrect conditions
+   - **Security**: unsanitized input, hardcoded secrets, missing auth checks
+   - **Performance**: N+1 queries, unnecessary loops, missing memoization
+   - **Style**: naming conventions, consistency with existing patterns
+   - **Tests**: do the changed functions have test coverage?
+
+4. **Verify** — run relevant tests and lints:
+   - `bash("npm test -- --testPathPattern=<related>")` for affected tests
+   - `bash("npm run lint")` if lint script exists
+
+5. **Deliver findings** as structured text:
+   - Severity: 🔴 Critical / 🟡 Warning / 🔵 Suggestion
+   - File path and line reference for each finding
+   - Specific recommendation for each issue
+
+## Anti-patterns to avoid
+- Don't re-read entire files that haven't changed
+- Don't list style issues that the formatter would catch
+- Don't make edits during review — review is read-only by default

package/dist/skills/refactoring.md

@@ -0,0 +1,40 @@
+# Refactoring Skill
+<!-- trigger: refactor, rewrite, restructure, clean up, cleanup -->
+<!-- trigger: simplify, extract function, extract method, extract class -->
+<!-- trigger: rename, move to, split into, consolidate, modernize -->
+
+## Instructions
+
+When activated for refactoring, follow this tool sequence:
+
+1. **Map all usages first** — never change a signature without finding callers:
+   - `grep(<function_name>, "src/")` to find all call sites
+   - `grep(<class_name>, "src/")` for class references
+   - `grep("import.*<module>", "src/")` for import statements
+
+2. **Understand the current structure**:
+   - `read_file` the core file being refactored
+   - `read_file` 2-3 representative callers (not all of them yet)
+   - For large refactors, use `task_list` to track sub-tasks
+
+3. **Make the core change**:
+   - Edit the primary file first with `edit_file` or `write_file`
+   - Keep the change minimal — one concern per edit
+   - Verify the core change compiles: `bash("npx tsc --noEmit")` or similar
+
+4. **Update callers** (parallel where possible):
+   - For each caller: `read_file` (targeted lines) → `edit_file` → next
+   - Batch independent edits into a single turn
+   - For many callers (>3), consider `spawn_agents` for parallel updates
+
+5. **Verify completeness**:
+   - `grep(<old_name>)` to check no stale references remain
+   - `bash("npm test")` to run the full suite
+   - `git_diff` to review the full change set
+
+## Safety rules
+
+- **Never refactor without tests**: if tests don't exist, write at least a smoke test first
+- **One refactor per session**: don't mix refactoring with feature addition
+- **Check git status first**: ensure a clean starting point
+- **Commit small, logical units**: refactor → test → commit, then next refactor

package/dist/skills/testing.md

@@ -0,0 +1,39 @@
+# Testing Skill
+<!-- trigger: test, testing, write test, add test, create test, test coverage -->
+<!-- trigger: unit test, integration test, e2e test, test suite -->
+<!-- trigger: failing test, broken test, test failure -->
+
+## Instructions
+
+When activated for testing, follow this tool sequence:
+
+1. **Understand what to test**:
+   - `read_file` the source file that needs tests
+   - `grep` for existing test files: `grep(<source_filename>, "tests/")`
+   - If a test file exists, read it to match patterns
+
+2. **Determine the test framework** (check package.json or config files):
+   - Jest: `jest.config.*`, `"jest"` in package.json → `npm test -- --testPathPattern=...`
+   - Vitest: `vitest.config.*` → `npx vitest run`
+   - Mocha: `.mocharc.*`, `"mocha"` in package.json → `npx mocha`
+   - If unsure, check `package.json scripts.test` for the command
+
+3. **Write the test**:
+   - Follow existing test patterns (read a similar test file first)
+   - Cover: happy path, edge cases, error conditions
+   - Use `write_file` for new test files, `edit_file` for adding to existing ones
+   - Name pattern: `<source_name>.test.<ext>` or `<source_name>.spec.<ext>`
+
+4. **Run the test**:
+   - `bash("npm test -- --testPathPattern=<test_file>")` for Jest/Vitest
+   - Check output for pass/fail
+   - If it fails, read the error, fix the test or source, re-run
+
+5. **Verify coverage** (if available):
+   - `bash("npm test -- --coverage")` and check the report
+
+## Quick patterns
+
+- **Add test to existing suite**: read_test → edit_file (add test case) → bash(test)
+- **Create new test file**: read_source → read_similar_test → write_file → bash(test)
+- **Fix failing test**: read_test → read_source → edit_file (fix) → bash(test)

package/examples/bug-fix.md

@@ -0,0 +1,16 @@
+<!-- Few-shot example: bug-fix
+     Used by cli/few-shot.js — keep under 250 tokens total.
+     Demonstrates the Bug-Fix Pattern: read error → grep for symbol → read target file → edit → verify -->
+
+user: The login handler throws TypeError: Cannot read properties of undefined, can you fix it?
+
+A: |
+  I'll trace the error through the codebase.
+  Step 1 — grep for the error source (use line numbers for targeted reads):
+  → grep("TypeError", "src/handlers/")
+  Step 2 — read only the matched line range:
+  → read_file("src/handlers/login.js", line_start=18, line_end=30)
+  Step 3 — edit the specific lines that cause the crash:
+  → edit_file("src/handlers/login.js", old_string, new_string)
+  Step 4 — verify the fix with the relevant test:
+  → bash("npm test -- --testPathPattern=login")

package/examples/feature-add.md

@@ -0,0 +1,20 @@
+<!-- Few-shot example: feature-add
+     Used by cli/few-shot.js — keep under 250 tokens total.
+     Demonstrates the Feature-Add Pattern: read existing pattern → edit one file → verify → done -->
+
+user: Add a rate limiter middleware to the Express server
+
+A: |
+  I'll find the existing middleware pattern, then add the new one.
+  Step 1 — read an existing middleware to match patterns:
+  → read_file("src/middleware/auth.js")
+  Step 2 — create the new middleware following the same structure:
+  → write_file("src/middleware/rateLimiter.js", ...)
+  Step 3 — register it where other middleware is wired (grep for app.use pattern):
+  → grep("app.use", "src/server.js")
+  Step 4 — read the server file around the middleware registration:
+  → read_file("src/server.js", line_start=10, line_end=25)
+  Step 5 — add the new middleware registration:
+  → edit_file("src/server.js", old_string, new_string)
+  Step 6 — verify the server still starts:
+  → bash("npm test")

package/examples/refactor.md

@@ -0,0 +1,19 @@
+<!-- Few-shot example: refactor
+     Used by cli/few-shot.js — keep under 250 tokens total.
+     Demonstrates the Refactor Pattern: grep for all usages → read callers → edit core → update callers -->
+
+user: Refactor the getUser function to accept an options object instead of positional arguments
+
+A: |
+  I'll find all usages before changing the signature.
+  Step 1 — grep for all call sites:
+  → grep("getUser(", "src/")
+  Step 2 — read the function definition and a couple callers:
+  → read_file("src/services/user.js", line_start=45, line_end=70)
+  Step 3 — refactor the function signature:
+  → edit_file("src/services/user.js", old_signature, new_signature)
+  Step 4 — update each caller (read → edit):
+  → read_file("src/controllers/profile.js", line_start=30, line_end=50)
+  → edit_file("src/controllers/profile.js", old_call, new_call)
+  Step 5 — verify all tests still pass:
+  → bash("npm test -- --testPathPattern=user")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nex-code",
-  "version": "0.5.27",
+  "version": "0.5.28",
   "description": "Run 400B+ open coding models on your codebase without the hardware bill. Ollama Cloud first — OpenAI, Anthropic, and Gemini when you need them.",
   "bin": {
     "nex-code": "./dist/nex-code.js"