vivekmind 0.15.6

package/bundled/batch/SKILL.md

@@ -0,0 +1,304 @@
+---
+name: batch
+description: Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use `/batch` followed by operation and file pattern.
+argument-hint: '<operation> <file-pattern>'
+allowedTools:
+  - task
+  - glob
+  - grep_search
+  - read_file
+  - edit
+  - write_file
+  - run_shell_command
+  - ask_user_question
+---
+
+# /batch - Parallel Batch Operations
+
+You are orchestrating a batch operation across multiple files. Your job is to:
+
+1. Parse the user's request to understand the target files and operation
+2. Discover matching files using glob
+3. Split files into chunks for parallel processing
+4. Launch multiple worker agents to process files concurrently
+5. Aggregate results and present a summary
+
+## Step 1: Parse Intent and Discover Files
+
+First, parse the user's request to identify:
+
+- **Target pattern**: glob pattern for files (e.g., `src/**/*.ts`, `**/*.js`)
+- **Operation**: what to do with each file (e.g., "add JSDoc comments", "convert to TypeScript")
+
+If the user didn't specify a pattern, infer it from context or ask for clarification.
+
+Use the `glob` tool to discover matching files.
+
+**If no files match the pattern**:
+
+- Inform the user that no files were found for the given pattern
+- Suggest checking the pattern or broadening the search scope
+- Do not proceed with an empty batch
+
+Apply these common exclusions automatically:
+
+- `node_modules/**`
+- `dist/**`
+- `build/**`
+- `.git/**`
+- `**/*.test.ts`, `**/*.test.js`
+- `**/*.spec.ts`, `**/*.spec.js`
+- `**/__tests__/**`
+- `**/test/**`, `**/tests/**`
+- `**/package-lock.json`
+- `**/yarn.lock`
+- `**/*.min.js`
+- Binary files (images, fonts, etc.)
+- Files larger than 500KB (check size if needed)
+
+**Important**: If more than 50 files match, inform the user with the exact count and the file list, then proceed. The user can cancel (Ctrl+C) if needed. If the count exceeds 100 files, warn the user and suggest a more specific pattern instead of proceeding.
+
+## Step 2: Chunk Files for Parallel Processing
+
+Split the discovered files into chunks based on these rules:
+
+| Total Files | Chunk Count | Files Per Chunk |
+| ----------- | ----------- | --------------- |
+| 1-5         | 1           | All files       |
+| 6-15        | 2           | 3-8 each        |
+| 16-30       | 3           | ~10 each        |
+| 31-50       | 4           | ~10-12 each     |
+| 51-75       | 5           | ~10-15 each     |
+| 76-100      | 5           | ~15-20 each     |
+
+**Chunking algorithm**:
+
+- Minimum chunk size: 3 files (avoid over-parallelization for small batches)
+- Maximum chunk size: 15 files (ensure reasonable work per agent)
+- Maximum parallel agents: 5 (API rate limit consideration)
+
+Example: 24 files → 3 chunks of ~8 files each
+
+## Step 3: Launch Parallel Worker Agents
+
+Launch worker agents **in parallel** by invoking the `task` tool (the Agent tool) multiple times in a **SINGLE message**.
+
+**Note**: The `task` tool in allowedTools is the Agent tool used to spawn worker agents.
+
+Each worker agent should receive:
+
+- The list of files to process (full paths)
+- The operation to perform
+- Clear instructions to report success/failure per file
+
+Use the `general-purpose` subagent type for workers.
+
+**CRITICAL**: All Agent tool calls MUST be in a single response to enable parallel execution. The system automatically runs multiple Agent calls concurrently.
+
+### Agent Prompt Template
+
+For each chunk, use this prompt format:
+
+```
+You are a worker agent processing a batch of files.
+
+**Operation**: [describe the operation, e.g., "Add JSDoc comments to all exported functions"]
+
+**Files to process**:
+- [file1.ts]
+- [file2.ts]
+- ...
+
+**Instructions**:
+1. Process each file independently
+2. For each file, report one of:
+   - SUCCESS: [file path] - [brief description of change]
+   - FAILED: [file path] - [reason for failure]
+   - SKIPPED: [file path] - [reason for skipping]
+3. If a file fails or is skipped, continue with the next file - do not abort
+4. At the end, provide a summary of what was done
+
+**Constraints**:
+- Do not modify test files unless explicitly requested
+- Preserve existing code style and formatting
+- Make minimal necessary changes to accomplish the operation
+```
+
+### Example Invocation Pattern
+
+```
+<Agent tool call 1>
+description: "Process batch chunk 1/3"
+prompt: "You are a worker agent... [full prompt as above]"
+subagent_type: "general-purpose"
+</Agent tool call 1>
+
+<Agent tool call 2>
+description: "Process batch chunk 2/3"
+prompt: "You are a worker agent... [full prompt as above]"
+subagent_type: "general-purpose"
+</Agent tool call 2>
+
+<Agent tool call 3>
+description: "Process batch chunk 3/3"
+prompt: "You are a worker agent... [full prompt as above]"
+subagent_type: "general-purpose"
+</Agent tool call 3>
+```
+
+## Step 4: Aggregate Results
+
+After all worker agents complete, aggregate their results into a clear summary.
+
+### Output Format
+
+```markdown
+### Batch Operation Complete
+
+**Operation**: [description of what was done]
+**Files discovered**: [total count]
+**Chunks processed**: [number of parallel agents]
+**Total time**: [duration if tracked]
+
+| Status  | Count |
+| ------- | ----- |
+| Success | [N]   |
+| Failed  | [N]   |
+| Skipped | [N]   |
+
+**Successful files**:
+
+- [file1.ts] - [brief description]
+- [file2.ts] - [brief description]
+  ...
+
+**Failed files** (if any):
+
+- [file.ts]: [reason for failure]
+
+**Skipped files** (if any):
+
+- [file.ts]: [reason for skipping]
+```
+
+### Handling Partial Failures
+
+If some files failed but others succeeded:
+
+- Clearly report which files succeeded
+- List failures with specific reasons
+- Suggest follow-up actions if appropriate
+
+If all files failed:
+
+- Report the common failure pattern
+- Suggest potential fixes
+
+## Step 5: Error Handling
+
+### During Batch Processing
+
+1. **Single file failure**: Don't abort the batch. The worker agent records the error and continues.
+2. **Agent failure**: If a worker agent fails completely (timeout, crash), note the chunk as failed with reason.
+3. **User cancellation**: If the user sends Ctrl+C, the system will cancel all pending agents gracefully.
+
+### Error Reporting
+
+For each failed file, include:
+
+- File path
+- Specific error message or reason
+- Suggested fix if obvious
+
+## Usage Examples
+
+### Example 1: Add License Headers
+
+```
+/batch Add Apache 2.0 license header to all .ts files in src/
+```
+
+**Flow**:
+
+1. glob `src/**/*.ts` → find 45 files
+2. Split into 4 chunks
+3. Launch 4 parallel agents
+4. Each agent adds the license header to its assigned files
+5. Summary: 45 files processed, 45 succeeded, 0 failed
+
+### Example 2: Convert JavaScript to TypeScript
+
+```
+/batch Convert all .js files in utils/ to TypeScript
+```
+
+**Flow**:
+
+1. glob `utils/**/*.js` → find 12 files
+2. Split into 2 chunks
+3. Launch 2 parallel agents
+4. Each agent converts files and renames to .ts
+5. Summary: 12 files processed, 10 succeeded, 2 failed (complex dynamic patterns)
+
+### Example 3: Fix Lint Errors
+
+```
+/batch Fix all @typescript-eslint/no-explicit-any errors in src/
+```
+
+**Flow**:
+
+1. Use `grep_search` to find files containing `: any` pattern in `src/`
+2. Filter to relevant files
+3. Split into chunks and launch parallel agents
+4. Each agent fixes the specific lint issue (replace `any` with proper types)
+5. Summary: 8 files fixed
+
+## Constraints and Limits
+
+| Constraint          | Value | Reason                       |
+| ------------------- | ----- | ---------------------------- |
+| Max files per batch | 100   | Prevent resource exhaustion  |
+| Max parallel agents | 5     | API rate limit consideration |
+| Min files per agent | 3     | Avoid over-parallelization   |
+| Max files per agent | 15    | Ensure meaningful work       |
+| File size limit     | 500KB | Avoid context overflow       |
+
+## Dry-Run Mode
+
+If the user wants to preview what will be changed without actually modifying files (e.g., "preview", "show me what would change", "dry run"):
+
+1. Discover and list all matching files with counts
+2. Show the planned operation for each file
+3. Display the chunking strategy
+4. Ask the user if they want to proceed with the actual changes
+5. If user confirms, execute the batch operation
+
+**Example**:
+
+```
+/batch preview adding JSDoc comments to src/**/*.ts
+```
+
+**Expected output**:
+
+```
+### Dry-Run Preview
+
+**Operation**: Add JSDoc comments to all .ts files in src/
+
+**Files discovered**: 24 files
+
+**Chunking plan**:
+| Chunk | Files |
+|-------|-------|
+| 1     | src/utils/a.ts, b.ts, c.ts, ... (8 files) |
+| 2     | src/components/x.ts, y.ts, ... (8 files) |
+| 3     | src/services/m.ts, n.ts, ... (8 files) |
+
+**Planned operation per file**:
+- Add JSDoc comments to all exported functions
+- Preserve existing code style
+
+Proceed? (y/n)
+```

package/bundled/loop/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: loop
+description: Create a recurring loop that runs a prompt on a schedule. Usage - /loop 5m check the build, /loop check the PR every 30m, /loop run tests (defaults to 10m). /loop list to show jobs, /loop clear to cancel all.
+argument-hint: '[interval] <prompt> | list | clear'
+allowedTools:
+  - cron_create
+  - cron_list
+  - cron_delete
+---
+
+# /loop — schedule a recurring prompt
+
+## Subcommands
+
+If the input (after stripping the `/loop` prefix) is exactly one of these keywords, run the subcommand instead of scheduling:
+
+- **`list`** — call CronList and display the results. Done.
+- **`clear`** — call CronList, then call CronDelete for every job returned. Confirm how many were cancelled. Done.
+
+Otherwise, parse the input below into `[interval] <prompt…>` and schedule it with CronCreate.
+
+## Parsing (in priority order)
+
+1. **Leading token**: if the first whitespace-delimited token matches `^\d+[smhd]$` (e.g. `5m`, `2h`), that's the interval; the rest is the prompt.
+2. **Trailing "every" clause**: otherwise, if the input ends with `every <N><unit>` or `every <N> <unit-word>` (e.g. `every 20m`, `every 5 minutes`, `every 2 hours`), extract that as the interval and strip it from the prompt. Only match when what follows "every" is a time expression — `check every PR` has no interval.
+3. **Default**: otherwise, interval is `10m` and the entire input is the prompt.
+
+If the resulting prompt is empty, show usage `/loop [interval] <prompt>` and stop — do not call CronCreate.
+
+Examples:
+
+- `5m /babysit-prs` → interval `5m`, prompt `/babysit-prs` (rule 1)
+- `check the deploy every 20m` → interval `20m`, prompt `check the deploy` (rule 2)
+- `run tests every 5 minutes` → interval `5m`, prompt `run tests` (rule 2)
+- `check the deploy` → interval `10m`, prompt `check the deploy` (rule 3)
+- `check every PR` → interval `10m`, prompt `check every PR` (rule 3 — "every" not followed by time)
+- `5m` → empty prompt → show usage
+
+## Interval → cron
+
+Supported suffixes: `s` (seconds, rounded up to nearest minute, min 1), `m` (minutes), `h` (hours), `d` (days). Convert:
+
+| Interval pattern  | Cron expression        | Notes                                     |
+| ----------------- | ---------------------- | ----------------------------------------- |
+| `Nm` where N ≤ 59 | `*/N * * * *`          | every N minutes                           |
+| `Nm` where N ≥ 60 | `0 */H * * *`          | round to hours (H = N/60, must divide 24) |
+| `Nh` where N ≤ 23 | `0 */N * * *`          | every N hours                             |
+| `Nd`              | `0 0 */N * *`          | every N days at midnight local            |
+| `Ns`              | treat as `ceil(N/60)m` | cron minimum granularity is 1 minute      |
+
+**If the interval doesn't cleanly divide its unit** (e.g. `7m` → `*/7 * * * *` gives uneven gaps at :56→:00; `90m` → 1.5h which cron can't express), pick the nearest clean interval and tell the user what you rounded to before scheduling.
+
+## Action
+
+1. Call CronCreate with:
+   - `cron`: the expression from the table above
+   - `prompt`: the parsed prompt from above, verbatim (slash commands are passed through unchanged)
+   - `recurring`: `true`
+2. Briefly confirm: what's scheduled, the cron expression, the human-readable cadence, that recurring tasks auto-expire after 3 days, and that they can cancel sooner with CronDelete (include the job ID).
+3. **Then immediately execute the parsed prompt now** — don't wait for the first cron fire. If it's a slash command, invoke it via the Skill tool; otherwise act on it directly.
+
+## Input

package/bundled/qc-helper/SKILL.md

@@ -0,0 +1,152 @@
+---
+name: qc-helper
+description: Answer any question about VivekMind usage, features, configuration, and troubleshooting by referencing the official user documentation. Also helps users view or modify their settings.json. Invoke with `/qc-helper` followed by a question, e.g. `/qc-helper how do I configure MCP servers?` or `/qc-helper change approval mode to yolo`.
+argument-hint: '<question>'
+allowedTools:
+  - read_file
+  - edit_file
+  - grep_search
+  - glob
+  - read_many_files
+---
+
+# VivekMind Helper
+
+You are a helpful assistant for **VivekMind** — an AI coding agent for the terminal. Your job is to answer user questions about VivekMind's usage, features, configuration, and troubleshooting by referencing the official documentation, and to help users modify their configuration when requested.
+
+## How to Find Documentation
+
+The official user documentation is available in the `docs/` subdirectory **relative to this skill's directory**. Use the `read_file` tool to load the relevant document on demand by concatenating this skill's base directory path with the relative doc path listed below.
+
+> **Example**: If the user asks about MCP servers, read `docs/features/mcp.md` (relative to this skill's directory).
+
+---
+
+## Documentation Index
+
+Use this index to locate the right document for the user's question. Load only the docs that are relevant — do not read everything at once.
+
+### Getting Started
+
+| Topic             | Doc Path                  |
+| ----------------- | ------------------------- |
+| Product overview  | `docs/overview.md`        |
+| Quick start guide | `docs/quickstart.md`      |
+| Common workflows  | `docs/common-workflow.md` |
+
+### Configuration
+
+| Topic                                     | Doc Path                                |
+| ----------------------------------------- | --------------------------------------- |
+| Settings reference (all config keys)      | `docs/configuration/settings.md`        |
+| Authentication setup                      | `docs/configuration/auth.md`            |
+| Model providers (OpenAI-compatible, etc.) | `docs/configuration/model-providers.md` |
+| .vivekmindignore file                          | `docs/configuration/qwen-ignore.md`     |
+| Themes                                    | `docs/configuration/themes.md`          |
+| Memory                                    | `docs/configuration/memory.md`          |
+| Trusted folders                           | `docs/configuration/trusted-folders.md` |
+
+### Features
+
+| Topic                                       | Doc Path                         |
+| ------------------------------------------- | -------------------------------- |
+| Approval mode (plan/default/auto_edit/yolo) | `docs/features/approval-mode.md` |
+| MCP (Model Context Protocol)                | `docs/features/mcp.md`           |
+| Skills system                               | `docs/features/skills.md`        |
+| Sub-agents                                  | `docs/features/sub-agents.md`    |
+| Sandbox / security                          | `docs/features/sandbox.md`       |
+| Slash commands                              | `docs/features/commands.md`      |
+| Headless / non-interactive mode             | `docs/features/headless.md`      |
+| LSP integration                             | `docs/features/lsp.md`           |
+| Checkpointing                               | `docs/features/checkpointing.md` |
+| Token caching                               | `docs/features/token-caching.md` |
+| Language / i18n                             | `docs/features/language.md`      |
+| Arena mode                                  | `docs/features/arena.md`         |
+
+### IDE Integration
+
+| Topic                   | Doc Path                                     |
+| ----------------------- | -------------------------------------------- |
+| VS Code integration     | `docs/integration-vscode.md`                 |
+| Zed IDE integration     | `docs/integration-zed.md`                    |
+| JetBrains integration   | `docs/integration-jetbrains.md`              |
+| GitHub Actions          | `docs/integration-github-action.md`          |
+| IDE companion spec      | `docs/ide-integration/ide-companion-spec.md` |
+| IDE integration details | `docs/ide-integration/ide-integration.md`    |
+
+### Extensions
+
+| Topic                           | Doc Path                                       |
+| ------------------------------- | ---------------------------------------------- |
+| Extension introduction          | `docs/extension/introduction.md`               |
+| Getting started with extensions | `docs/extension/getting-started-extensions.md` |
+| Releasing extensions            | `docs/extension/extension-releasing.md`        |
+
+### Reference & Support
+
+| Topic                      | Doc Path                               |
+| -------------------------- | -------------------------------------- |
+| Keyboard shortcuts         | `docs/reference/keyboard-shortcuts.md` |
+| Troubleshooting            | `docs/support/troubleshooting.md`      |
+| Uninstall guide            | `docs/support/Uninstall.md`            |
+| Terms of service & privacy | `docs/support/tos-privacy.md`          |
+
+---
+
+## Configuration Quick Reference
+
+When the user asks about configuration, the primary reference is `docs/configuration/settings.md`. Here is a quick orientation:
+
+### Config File Locations & Priority
+
+| Level   | Path                                                         | Description                            |
+| ------- | ------------------------------------------------------------ | -------------------------------------- |
+| User    | `~/.vivekmind/settings.json`                                      | Personal global config                 |
+| Project | `<project>/.vivekmind/settings.json`                              | Project-specific, overrides user level |
+| System  | macOS: `/Library/Application Support/QwenCode/settings.json` | Admin-level config                     |
+
+**Priority** (highest to lowest): CLI args > env vars > system settings > project settings > user settings > defaults
+
+**Format**: JSON with Comments (supports `//` and `/* */`), with environment variable interpolation (`$VAR` or `${VAR}`)
+
+### Common Config Categories
+
+| Category      | Key Config Keys                                                               | Reference                                                                 |
+| ------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
+| Permissions   | `permissions.allow/ask/deny`                                                  | `docs/configuration/settings.md`, `docs/features/approval-mode.md`        |
+| MCP Servers   | `mcpServers.*`, `mcp.*`                                                       | `docs/configuration/settings.md`, `docs/features/mcp.md`                  |
+| Tool Approval | `tools.approvalMode`                                                          | `docs/configuration/settings.md`, `docs/features/approval-mode.md`        |
+| Model         | `model.name`, `modelProviders`                                                | `docs/configuration/settings.md`, `docs/configuration/model-providers.md` |
+| General/UI    | `general.*`, `ui.*`, `ide.*`, `output.*`                                      | `docs/configuration/settings.md`                                          |
+| Context       | `context.*`                                                                   | `docs/configuration/settings.md`                                          |
+| Advanced      | `hooks`, `env`, `webSearch`, `security`, `privacy`, `telemetry`, `advanced.*` | `docs/configuration/settings.md`                                          |
+
+---
+
+## Workflow
+
+### Answering Questions
+
+1. **Identify the topic** from the user's question using the Documentation Index above
+2. **Use `read_file`** to load the relevant doc(s) — only load what you need
+3. **Provide a clear, concise answer** grounded in the documentation content
+4. If the docs don't cover the question, say so honestly and suggest where to look
+
+### Helping with Configuration Changes
+
+When the user wants to modify their configuration:
+
+1. **Read the relevant doc** to understand the config key, its type, allowed values, and defaults
+2. **Ask which config level** to modify if not specified: user (`~/.vivekmind/settings.json`) or project (`.vivekmind/settings.json`)
+3. **Use `read_file`** to check the current content of the target settings file
+4. **Use `edit_file`** to apply the change with correct JSON syntax
+5. **After every configuration change**, you MUST remind the user:
+
+> **Note: Most configuration changes require restarting VivekMind (`/exit` then re-launch) to take effect.** Only a few settings (like `permissions`) are picked up dynamically.
+
+### Important Notes
+
+- Always ground your answers in the actual documentation content — do not guess or fabricate config keys
+- When showing config examples, use JSONC format with comments for clarity
+- If a question spans multiple topics (e.g., "How do I set up MCP with sandbox?"), read both relevant docs
+- For migration questions from other tools (Claude Code, Gemini CLI, etc.), check `docs/configuration/settings.md` for equivalent config keys