Structured Debugging
Hypothesis-driven debugging methodology for hard bugs. Use this
5,473,026 AI resources indexedWorking toward the world’s largest AI resource index.
Reusable instructions for compatible AI agents.
Field counts come from the latest full-catalog snapshot. A resource can belong to several fields and platforms.
Hypothesis-driven debugging methodology for hard bugs. Use this
Use Qwen Code as a Code Agent for code understanding, project
Workflow for creating new applications from scratch. Covers requirements gathering, tech stack selection, scaffolding, implementation, and delivery of a functional prototype.
This skill should be used when the user asks to "用 tmux 做真实测试", "保存 tmux 日志", "像真实用户一样测试 Qwen", "生成可复查的 TUI 测试报告", "测试 slash command 交互", or requests a tmux-based real user E2E run with complete readable logs. It guides real TUI usage with step-by-step capture-pane snapshots rather than ANSI raw ...
End-to-end workflow for implementing a non-trivial qwen-code
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, confli...
Fix a bug from a GitHub issue, following the reproduce-first
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API ...
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.
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and
Automates terminal UI screenshot testing for CLI commands. Applies
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck <PID> to focus on a specific process.
Try a broader search or clear some filters.
Platform labels describe intended use. Read each resource's author credits, requirements and available access methods.