/qwen-coder

name: qwen-coder
description: Provides Qwen Coder CLI delegation workflows for coding tasks using Qwen2.5-Coder and QwQ models, including English prompt formulation, execution flags, and safe result handling. Use when the user explicitly asks to use Qwen for tasks such as code generation, refactoring, debugging, or architectural analysis. Triggers on "use qwen", "use qwen coder", "delegate to qwen", "ask qwen", "second opinion from qwen", "qwen opinion", "continue with qwen", "qwen session".
allowed-tools: Bash, Read, Write

Qwen Coder CLI Delegation

Delegate selected tasks from Claude Code to Qwen Coder CLI using non-interactive commands, explicit model selection, safe permission flags, and shareable outputs.

Overview

This skill standardizes delegation to Qwen Coder CLI (`qwen`) for cases where Qwen's specific strengths may benefit the task. It covers:

• Non-interactive execution with `-p` / `--prompt`
• Model selection with `-m` / `--model`
• Approval control (`--approval-mode`)
• Session continuation with `-c` / `--continue` or `-r` / `--resume`
• Output format options (`text`, `json`, `stream-json`)

Use this skill only when delegation to Qwen Coder is explicitly requested or clearly beneficial.

When to Use

Use this skill when:

• The user asks to delegate work to Qwen Coder CLI
• The user wants a second opinion from Qwen Coder on a task
• The user asks for Qwen Coder CLI output integrated into the current workflow
• The user wants to continue a previous Qwen Coder session

Trigger phrases:

• "use qwen"
• "use qwen coder"
• "delegate to qwen"
• "ask qwen"
• "second opinion from qwen"
• "qwen opinion"
• "continue with qwen"
• "qwen session"

Prerequisites

Verify tool availability and authentication before delegation:

# CLI availability
qwen --version

# Authentication status
qwen auth status

If `qwen` is unavailable, inform the user and stop execution until Qwen Coder CLI is installed. If authentication is invalid, provide authentication setup instructions and stop execution.

Reference

• Command reference: `references/cli-command-reference.md`

Instructions

1) Confirm Delegation Scope

Before running Qwen Coder:

• Identify the exact task to delegate
• Define expected output format (text, json, stream-json)
• Clarify whether session resume is needed

If scope is ambiguous, ask for clarification first.

2) Formulate Prompt in English

All delegated prompts to Qwen Coder CLI must be in English.

Build a precise English prompt from the user request.

Prompt quality checklist:

• Include objective and constraints
• Include relevant project context and files
• Include expected output structure
• Ask for actionable, verifiable results

Prompt template:

Task: <clear objective>
Context: <project/module/files>
Constraints: <do/don't constraints>
Expected output: <format + depth>
Validation: <tests/checks to run or explain>

3) Select Execution Mode and Flags

Preferred baseline command:

qwen -p "<english-prompt>"

Supported options:

• `-m, --model <model-id>` for model selection (default: qwen2.5-coder)
• `--approval-mode <plan|default|auto_edit|yolo>` for safety control
• `-c, --continue <session-id>` to continue previous session
• `-r, --resume <session-id>` as alias for continue
• `-o, --output-format <text|json|stream-json>` for output format

Approval modes:

| Mode | Behavior | Recommended For | |------|----------|-----------------| | `plan` | Read-only analysis, no file modifications | Analysis-only tasks, security reviews | | `default` | Requires confirmation before modifications | General coding tasks | | `auto_edit` | Auto-approves edit operations | Trusted modifications with oversight | | `yolo` | Approves all operations without confirmation | Experimental tasks (explicit user request only) |

Safety guidance:

• Prefer `--approval-mode plan` for read-only analysis
• Use `--approval-mode default` for general tasks
• Reserve `--yolo` for explicit user requests only

4) Execute Qwen Coder CLI

Run the selected command via Bash and capture stdout/stderr.

Examples:

# Default non-interactive delegation
qwen -p "Analyze this code and suggest refactoring improvements."

# Explicit model and approval mode
qwen -p "Review authentication module for security issues with fixes." -m qwq --approval-mode plan

# Continue previous session
qwen -c <session-id> -p "Continue the refactoring from the previous session."

# Structured output for automation
qwen -p "Summarize key technical debt items as JSON array." --output-format json

5) Result Handling

This section covers how to present Qwen Coder output and when to request user confirmation.

5.1) Output Presentation

When reporting Qwen Coder output:

• Present output in a clear, readable format
• Summarize key findings and confidence level
• Separate observations from recommended actions
• Keep raw output available when needed
• Include the model used and approval mode applied
• State which permission profile was in effect

5.2) Confirmation Workflow

Before applying any suggested modifications:

1. Present the proposed changes to the user in the output template format 2. Request explicit confirmation (for example: "Do you want me to apply these changes?") 3. Wait for user direction before proceeding 4. Do not auto-apply changes without user consent

Exception: In `--approval-mode yolo` with explicit user request, changes may proceed automatically. Still inform the user of what was done.

5.3) Result Metadata

Each delegation result shall include the following metadata:

| Field | Description | |-------|-------------| | Task summary | What was delegated to Qwen Coder | | Command | The qwen command executed (without sensitive parameters) | | Model | Which model was used (for example qwen2.5-coder, qwq) | | Approval mode | The approval mode applied (plan, default, auto_edit, yolo) | | Key findings | Observations and results f