OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add giuseppe-trisciuoglio/developer-kit --skill qwen-coder
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".
npx skills add giuseppe-trisciuoglio/developer-kit --skill qwen-coder
Delegate selected tasks from Claude Code to Qwen Coder CLI using non-interactive commands, explicit model selection, safe permission flags, and shareable outputs.
This skill standardizes delegation to Qwen Coder CLI (qwen) for cases where Qwen's specific strengths may benefit the task. It covers:
-p / --prompt-m / --model--approval-mode)-c / --continue or -r / --resumetext, json, stream-json)Use this skill only when delegation to Qwen Coder is explicitly requested or clearly beneficial.
Use this skill when:
Trigger phrases:
Verify tool availability and authentication before delegation:
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.
references/cli-command-reference.mdBefore running Qwen Coder:
If scope is ambiguous, ask for clarification first.
All delegated prompts to Qwen Coder CLI must be in English.
Build a precise English prompt from the user request.
Prompt quality checklist:
Prompt template:
Preferred baseline command:
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 formatApproval 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:
--approval-mode plan for read-only analysis--approval-mode default for general tasks--yolo for explicit user requests onlyRun the selected command via Bash and capture stdout/stderr.
Examples:
This section covers how to present Qwen Coder output and when to request user confirmation.
When reporting Qwen Coder output:
Before applying any suggested modifications:
Exception: In --approval-mode yolo with explicit user request, changes may proceed automatically. Still inform the user of what was done.
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 from Qwen Coder |
| Suggested next actions | Recommended follow-up steps (if applicable) |
Use this structure when returning delegated results:
Input:
Command:
Expected behavior:
Input:
Command:
Expected behavior:
Input:
Command:
Expected behavior:
Input:
Command:
Expected behavior:
Input:
Command:
Expected behavior:
Input:
Command:
Expected behavior:
Input:
Command:
Expected behavior:
qwen -p "<english-prompt>"# 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## Qwen Coder Delegation Result
### Task
[delegated task summary]
### Command
`qwen ...`
### Key Findings
- Finding 1
- Finding 2
### Suggested Next Actions
1. Action 1
2. Action 2
### Notes
- Output language from Qwen: English
- Requires user approval before applying code changesAnalyze the authentication module and identify security vulnerabilities.qwen -p "Analyze the authentication module for security vulnerabilities. Report only high-confidence issues with severity, file paths, and remediation steps." -m qwq --approval-mode planReturns a structured analysis with high-confidence security findings, including severity ratings and specific remediation recommendations.Refactor the payment service to reduce code duplication while keeping the public API unchanged.qwen -p "Refactor the payment service in src/services/payment.ts to reduce duplication. Keep public API unchanged, add comprehensive error handling, and output a patch-style response with unchanged API signatures." -m qwen2.5-coder --approval-mode defaultProposes concrete code changes (patch-style), extracts duplication into shared helpers, and maintains original API contracts.Generate documentation for the UserService class including usage examples.qwen -p "Generate comprehensive documentation for the UserService class. Include: class purpose, public methods with parameters, usage examples, and error handling patterns. Format as markdown." -m qwen2.5-coder --approval-mode planReturns markdown-formatted documentation with JSDoc-style comments, method signatures, and practical usage examples.Generate a REST API endpoint for CRUD operations on items.qwen -p "Generate a production-ready REST API endpoint for CRUD operations on items. Include input validation, error handling, and unit tests. Use Express.js framework." -m qwen2.5-coder --approval-mode auto_editGenerates complete, runnable code for POST/GET/PUT/DELETE endpoints with proper middleware, validation, and test scaffolding.Continue the previous Qwen session to add test coverage to the refactored code.qwen -c <session-id> -p "Continue from the previous session. Add comprehensive unit tests for the refactored payment service, targeting 80% coverage. Include mocks for external dependencies." -m qwen2.5-coder --approval-mode defaultResumes the previous session context and continues work, adding test files with appropriate mocks and assertions.Compare Qwen2.5-Coder and QwQ outputs for the same refactoring task.# First run with Qwen2.5-Coder
qwen -p "Refactor the string utility module for better maintainability." -m qwen2.5-coder --approval-mode plan --output-format text
# Then run with QwQ for comparison
qwen -p "Refactor the string utility module for better maintainability." -m qwq --approval-mode plan --output-format textProvides side-by-side comparison: Qwen2.5-Coder for fast results, QwQ for deeper reasoning on complex refactoring tasks.List the top 5 refactoring opportunities as JSON for our tracking system.qwen -p "Analyze this codebase and return the top 5 refactoring opportunities as a JSON array. Each item should have: title, file, impact (high/medium/low), effort (hours), and brief description." -m qwen2.5-coder --output-format jsonReturns valid JSON array with 5 refactoring items, parseable for integration with project management tools.