@protolabsai/proto 0.14.0

package/dist/bundled/finishing-a-development-branch/SKILL.md

@@ -0,0 +1,213 @@
+---
+name: finishing-a-development-branch
+description: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
+---
+
+# Finishing a Development Branch
+
+## Overview
+
+Guide completion of development work by presenting clear options and handling chosen workflow.
+
+**Core principle:** Verify tests → Present options → Execute choice → Clean up.
+
+**Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work."
+
+## The Process
+
+### Step 1: Verify Tests
+
+**Before presenting options, verify tests pass:**
+
+```bash
+# Run project's test suite
+npm test / cargo test / pytest / go test ./...
+```
+
+**If tests fail:**
+
+```
+Tests failing (<N> failures). Must fix before completing:
+
+[Show failures]
+
+Cannot proceed with merge/PR until tests pass.
+```
+
+Stop. Don't proceed to Step 2.
+
+**If tests pass:** Continue to Step 2.
+
+### Step 2: Determine Base Branch
+
+```bash
+# Try common base branches
+git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
+```
+
+Or ask: "This branch split from main - is that correct?"
+
+### Step 3: Present Options
+
+Present exactly these 4 options:
+
+```
+Implementation complete. What would you like to do?
+
+1. Merge back to <base-branch> locally
+2. Push and create a Pull Request
+3. Keep the branch as-is (I'll handle it later)
+4. Discard this work
+
+Which option?
+```
+
+**Don't add explanation** - keep options concise.
+
+### Step 4: Execute Choice
+
+#### Option 1: Merge Locally
+
+```bash
+# Switch to base branch
+git checkout <base-branch>
+
+# Pull latest
+git pull
+
+# Merge feature branch
+git merge <feature-branch>
+
+# Verify tests on merged result
+<test command>
+
+# If tests pass
+git branch -d <feature-branch>
+```
+
+Then: Cleanup worktree (Step 5)
+
+#### Option 2: Push and Create PR
+
+```bash
+# Push branch
+git push -u origin <feature-branch>
+
+# Create PR
+gh pr create --title "<title>" --body "$(cat <<'EOF'
+## Summary
+<2-3 bullets of what changed>
+
+## Test Plan
+- [ ] <verification steps>
+EOF
+)"
+```
+
+Then: Cleanup worktree (Step 5)
+
+#### Option 3: Keep As-Is
+
+Report: "Keeping branch <name>. Worktree preserved at <path>."
+
+**Don't cleanup worktree.**
+
+#### Option 4: Discard
+
+**Confirm first:**
+
+```
+This will permanently delete:
+- Branch <name>
+- All commits: <commit-list>
+- Worktree at <path>
+
+Type 'discard' to confirm.
+```
+
+Wait for exact confirmation.
+
+If confirmed:
+
+```bash
+git checkout <base-branch>
+git branch -D <feature-branch>
+```
+
+Then: Cleanup worktree (Step 5)
+
+### Step 5: Cleanup Worktree
+
+**For Options 1, 2, 4:**
+
+Check if in worktree:
+
+```bash
+git worktree list | grep $(git branch --show-current)
+```
+
+If yes:
+
+```bash
+git worktree remove <worktree-path>
+```
+
+**For Option 3:** Keep worktree.
+
+## Quick Reference
+
+| Option           | Merge | Push | Keep Worktree | Cleanup Branch |
+| ---------------- | ----- | ---- | ------------- | -------------- |
+| 1. Merge locally | ✓     | -    | -             | ✓              |
+| 2. Create PR     | -     | ✓    | ✓             | -              |
+| 3. Keep as-is    | -     | -    | ✓             | -              |
+| 4. Discard       | -     | -    | -             | ✓ (force)      |
+
+## Common Mistakes
+
+**Skipping test verification**
+
+- **Problem:** Merge broken code, create failing PR
+- **Fix:** Always verify tests before offering options
+
+**Open-ended questions**
+
+- **Problem:** "What should I do next?" → ambiguous
+- **Fix:** Present exactly 4 structured options
+
+**Automatic worktree cleanup**
+
+- **Problem:** Remove worktree when might need it (Option 2, 3)
+- **Fix:** Only cleanup for Options 1 and 4
+
+**No confirmation for discard**
+
+- **Problem:** Accidentally delete work
+- **Fix:** Require typed "discard" confirmation
+
+## Red Flags
+
+**Never:**
+
+- Proceed with failing tests
+- Merge without verifying tests on result
+- Delete work without confirmation
+- Force-push without explicit request
+
+**Always:**
+
+- Verify tests before offering options
+- Present exactly 4 options
+- Get typed confirmation for Option 4
+- Clean up worktree for Options 1 & 4 only
+
+## Integration
+
+**Called by:**
+
+- **subagent-driven-development** (Step 7) - After all tasks complete
+- **executing-plans** (Step 5) - After all batches complete
+
+**Pairs with:**
+
+- **using-git-worktrees** - Cleans up worktree created by that skill

package/dist/bundled/loop/SKILL.md

@@ -0,0 +1,61 @@
+---
+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.
+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/dist/bundled/qc-helper/SKILL.md

@@ -0,0 +1,151 @@
+---
+name: qc-helper
+description: Answer any question about Qwen Code 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`.
+allowedTools:
+  - read_file
+  - edit_file
+  - grep_search
+  - glob
+  - read_many_files
+---
+
+# Qwen Code Helper
+
+You are a helpful assistant for **Qwen Code** — an AI coding agent for the terminal. Your job is to answer user questions about Qwen Code'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` |
+| .qwenignore 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    | `~/.qwen/settings.json`                                      | Personal global config                 |
+| Project | `<project>/.qwen/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 (`~/.qwen/settings.json`) or project (`.qwen/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 Qwen Code (`/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

package/dist/bundled/qc-helper/docs/_meta.ts

@@ -0,0 +1,30 @@
+export default {
+  'Getting started': {
+    type: 'separator',
+    title: 'Getting started', // Title is optional
+  },
+  overview: 'Overview',
+  quickstart: 'QuickStart',
+  'common-workflow': 'Command Workflows',
+  'Outside of the terminal': {
+    type: 'separator',
+    title: 'Outside of the terminal', // Title is optional
+  },
+  'integration-vscode': 'Visual Studio Code',
+  'integration-zed': 'Zed IDE',
+  'integration-jetbrains': 'JetBrains IDEs',
+  'integration-github-action': 'Github Actions',
+  'Code with Qwen Code': {
+    type: 'separator',
+    title: 'Code with Qwen Code', // Title is optional
+  },
+  features: 'Features',
+  configuration: 'Configuration',
+  extension: 'Extension',
+  reference: 'Reference',
+  support: 'Support',
+  // need refine
+  'ide-integration': {
+    display: 'hidden',
+  },
+};