@vyuhlabs/dxkit 1.0.0 → 1.0.1

package/dist/constants.d.ts

@@ -1,5 +1,5 @@
 import { ResolvedConfig } from './types';
-export declare const VERSION = "1.0.0";
+export declare const VERSION = "1.0.1";
 export declare const DEFAULT_VERSIONS: {
     python: string;
     go: string;

package/dist/constants.js

@@ -3,7 +3,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.EVOLVING_FILES = exports.DEFAULT_COVERAGE = exports.DEFAULT_VERSIONS = exports.VERSION = void 0;
 exports.buildVariables = buildVariables;
 exports.buildConditions = buildConditions;
-exports.VERSION = '1.0.0';
+exports.VERSION = '1.0.1';
 exports.DEFAULT_VERSIONS = {
     python: '3.12',
     go: '1.24.0',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vyuhlabs/dxkit",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "AI-native developer experience toolkit for any repository",
   "license": "MIT",
   "bin": {

package/templates/.claude/agents-available/plan-executor.md

@@ -33,14 +33,19 @@ For each task in the plan:
 
 1. **Announce**: "Working on Task N: [title]"
 2. **Plan**: Explain what you'll do and why (reference the plan's reasoning)
-3. **Execute**: Make the changes
+3. **Pattern sweep (IMPORTANT)**: Before editing, grep for all similar occurrences of the pattern across the codebase. The plan may reference one specific file:line, but reports can miss duplicates. If you find additional matches that fit the same security/quality category:
+   - List them to the user and ask whether to fix all or only the listed ones
+   - Default to fixing ALL matches of the same class (e.g., all `console.log(secret)` patterns, not just the one line)
+   - Record the additional finds in the progress file so they're tracked
+4. **Execute**: Make the changes
    - Follow conventions from `.claude/rules/` and `.claude/skills/learned/`
    - Run quality checks after changes (`/quality` approach — same linters)
    - Run tests if applicable (`/test` approach — same test runner)
-4. **Verify**: Confirm the task is complete
+5. **Verify**: Confirm the task is complete
    - Run the plan's verification command if specified
    - Check that no new lint errors were introduced
-5. **Update progress**: Append to `.ai/plans/progress/<plan-name>.md`
+   - Re-run the pattern sweep to confirm no duplicates remain
+6. **Update progress**: Append to `.ai/plans/progress/<plan-name>.md`, noting any additional fixes beyond the plan scope
 
 ### Step 5: Checkpoint
 

package/templates/.claude/agents-available/strategic-planner.md

@@ -137,4 +137,5 @@ Use `/execute-plan <plan-name>` to start working through a plan with session man
 - **Prioritized** — security > correctness > quality > docs > DX
 - **Realistic** — tasks should be completable in 1-3 sessions each
 - **Specific** — name exact files, exact commands, exact patterns to fix
+- **Pattern-based, not line-based** — when a finding represents a class of issues (e.g., `console.log(secret)`, `eval(userInput)`), specify tasks as **patterns to sweep** not just one line. Include the grep pattern so the executor can find all occurrences. Example: "Remove all `console.log(.*secret|.*token|.*password)` across `src/` — 2 known instances at file:line plus any others"
 - Save plans to `.ai/plans/`