Qwen

Run a prompt immediately, then repeat it on a fixed schedule or when another check is useful. Use it to follow builds and pull requests, work through a task file, and list or cancel scheduled jobs.

• Check build status at regular intervals
• Follow up on a pull request
• Work through tasks stored in loop.md

Turn a vague request into a goal with one outcome, verifiable completion checks, boundaries, a stopping agreement, and instructions for blockers. It drafts the objective for review without starting the work described.

• Turning a vague intention into a verifiable goal
• Tightening the completion checks of an existing goal
• Defining boundaries and a stopping agreement

Review Qwen Code issues and pull requests through staged checks. Assess product fit, code simplicity, and CI evidence, then prepare English and Chinese comments that explain findings and flag decisions needing maintainer attention.

• Triage incoming Qwen Code issues
• Check pull requests against product direction
• Review changes for unnecessary complexity

Create a functional application prototype from an initial idea. The workflow covers requirements, technology choices, plan approval, project setup, implementation, visual assets where needed, build verification, and instructions for starting the result.

• Building a website prototype from an idea
• Creating an initial mobile or desktop application
• Developing a playable 2D or 3D game prototype

Prepare shared instructions for translating, rewriting, or extracting information from many independent files, then submit a plan through the DashScope Batch API. Processing runs asynchronously at half the realtime list price and delivers new files later.

• Translate many documents using shared terminology
• Rewrite independent files into a consistent format
• Extract structured data from a collection of files

Explore code structure and history using an index of code relationships and meaning-based search. Trace calls, assess change impact, find likely bug locations, generate architecture reports, and review pull requests for risk and conflicts.

• Tracing function calls and change impact
• Investigating code locations related to a GitHub issue
• Generating architecture reports and class diagrams

Turn a feature idea or bug description into a GitHub issue, informed by relevant code and existing issues. It prepares an English draft with a Chinese translation, incorporates feedback, and submits it with labels after explicit approval.

• Turning a feature idea into a GitHub issue
• Preparing a bug report using the project template
• Writing an issue in English and Chinese

Prepare pull request title and body files from the current branch diff and available test reports. Follow the repository template, include concrete reviewer checks, and provide an English body with a Chinese translation.

• Draft a pull request from current branch changes
• Prepare PR metadata files for CI or autofix
• Document reviewer checks and tested operating systems

Compare a feature implemented in Qwen Code with Codex or Claude Code under the same scenario. Capture communication and terminal records, inspect tool definitions and outputs, and guide fixes toward matching observable behavior.

• Checking a reproduced feature against its reference agent
• Comparing tool definitions and required arguments
• Investigating differences in terminal output

Guide substantial qwen-code feature development from investigation and design through implementation, testing, and review. Produce design documents and end-to-end test plans, compare behavior before and after changes, and address verified review findings.

• Developing features that span multiple files
• Documenting a design before implementation
• Comparing behavior before and after a change

Review local code changes with git diff and update the matching pages under docs/. Keep commands, settings, examples, and navigation aligned with current behavior so readers can understand the changes without reading the code.

• Documenting uncommitted feature changes
• Updating setup instructions after a refactor
• Replacing outdated commands and configuration examples

Create and customize Qwen Code extensions using templates for context, commands, skills, agents, and MCP servers that connect external tools. Validate configuration and referenced files, review executable behavior, and prepare the extension for local testing.

• Creating a Qwen Code extension from a template
• Packaging custom commands and skills in an extension
• Adding MCP servers or other extension integrations

Find unused components, files, translation keys, and other unnecessary code across a codebase. Document every consumer and removal impact in a tracking issue, then turn one maintainer-approved candidate into a focused pull request.

• Periodically checking for accumulated unused code
• Finding orphaned translation keys
• Recording removal candidates and their impact in an issue

Find alternative words and phrases that fit a sentence, audience, and tone. Suggestions distinguish close synonyms from related expressions, explain differences in meaning or formality, and include brief usage examples when helpful.

• Vary repeated words in a piece of writing
• Choose wording for formal or conversational contexts
• Compare subtle differences between similar words

Design charts, maps, and dashboards around the question readers need answered. Choose suitable chart forms, communicate findings through titles and labels, and check custom colors with a local palette validator to support clear visual distinctions.

• Choose a chart type for comparisons or trends
• Improve dashboard layout and number formatting
• Check a custom chart palette

Operate native applications on macOS, Windows, and Linux using Qwen Cua Driver. Inspect screenshots and structured interface elements, perform clicks, typing, menu actions, or window adjustments, and verify the resulting application state.

• Automating clicks and text entry in desktop apps
• Navigating native application menus
• Setting exact window positions and sizes

Automate terminal interactions and capture screenshots before and after commands run. Define scenarios in TypeScript to review CLI appearance, document command flows, or record changing output such as progress bars, with optional animated GIFs.

• Review CLI appearance changes in a pull request
• Capture slash command interactions
• Create screenshots for usage documentation

Stabilize a test that fails and then passes on the same commit. Apply a minimal fix to timing, randomness, clock behavior, or shared resources while preserving assertions, then verify it through repeated runs.

• Fixing tests that pass only after a rerun
• Improving timeout budgets and condition-based waiting
• Making clock-dependent or random tests deterministic