bahayonghang/qwen-companion
content/skills/developer-tools-integrations/qwen-companion/SKILL.md
Coordinate Qwen CLI companion workflows for staged review, bounded follow-up execution, and explicit continuation inside repository work. Use this skill when the user explicitly wants a Qwen-native companion process, wants help structuring Qwen review versus implementation, or needs a clear Qwen CLI workflow with scoped next steps instead of generic shell usage. Prefer this when the task is specifically about operating Qwen as a structured companion.
$ install --global
skillsauthnpx skillsauth add bahayonghang/my-claude-code-settings qwen-companionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:53 PM1.8s1 file scanned
SKILL.md
- name:
- qwen-companion
- description:
- >-
- version:
- 0.1.0
- category:
- developer-tools-integrations
- argument-hint:
- [task-or-workflow-goal]
Use this skill when the user wants a Qwen CLI companion workflow with explicit phases and careful scope control.
Best fit
Reach for qwen-companion when the user wants Qwen to:
- review or reason about a change before execution
- define the next bounded step in a multi-step task
- continue an earlier Qwen-guided flow with explicit limits
- operate as a structured companion rather than an ad-hoc command runner
Positioning
| Skill | Best for |
|---|---|
| qwen-companion | Structured Qwen CLI companion workflow |
| codex-companion | Codex runtime lifecycle and persistent task handling |
| claude-code-companion | Claude Code-native staged workflow |
| gemini-companion | Gemini CLI staged companion workflow |
Working model
Treat this skill as a workflow contract around Qwen CLI.
Do not claim provider-native persistent threads, resumable job ids, or Codex-style lifecycle commands unless the concrete Qwen environment truly supports them.
Suggested flow
- Clarify what the user wants Qwen to accomplish.
- Decide whether the right mode is:
- review-first,
- second-pass analysis,
- bounded execution,
- or continuation with explicit scope.
- Keep all continuity claims precise.
- Verify outcomes from repository state, diffs, or tests before concluding.
Guardrails
- Prefer explicit boundaries over vague autonomous claims.
- Keep tasks small and reviewable.
- Redirect Codex-style runtime lifecycle expectations to
codex-companion.
Related Skills
bahayonghang/codex-dynamic-workflows
development
VerifiedTrustedCommunity
Use only when the user explicitly asks for swarm, subagents, parallel agents, dynamic workflow, multi-agent orchestration, 多智能体编排, or when the task truly needs coordinated research plus implementation plus review plus verification packets. Do not use for ordinary code review, planning-only work, single-line bugfixes, routine audits, or migrations unless orchestration is requested or at least two independent workflow dimensions are present.
15SKILL.mdUpdated Jun 4, 2026
bahayonghang/code-quality-review
development
VerifiedTrustedCommunity
Run a code quality review focused on maintainability, structure, abstraction quality, file growth, branching complexity, boundary cleanliness, and refactoring opportunities. Use when the user asks for code quality review, code review, maintainability review, architecture quality review, PR code quality feedback, 代码质量审查, 代码质量 review, 可维护性审查, 架构质量审查, or review comments about code structure. Do not use for pure security review, formatting-only review, performance profiling, or implementation tasks unless the user also asks for a code quality review.
15SKILL.mdUpdated Jun 4, 2026
bahayonghang/spark
development
VerifiedTrustedCommunity
Plan-first brainstorming workflow that turns an idea into an approved Markdown implementation plan by default. Use when the user wants to brainstorm, design, scope, or plan a feature/spec before implementation. Spark explores project context, asks only blocking questions, writes the plan under the project root's .plannings/YYYY-MM-DD-feature-slug.md path, self-reviews it, and waits for user approval. Create an HTML or visual plan/spec only when the user explicitly asks for HTML, browser-viewable, or visual output; save the paired .html beside the Markdown plan.
15SKILL.mdUpdated May 29, 2026
bahayonghang/code-quality-review
development
VerifiedTrustedCommunity
Run a code quality review focused on maintainability, structure, abstraction quality, file growth, branching complexity, boundary cleanliness, and refactoring opportunities. Use when the user asks for code quality review, code review, maintainability review, architecture quality review, PR code quality feedback, 代码质量审查, 代码质量 review, 可维护性审查, 架构质量审查, or review comments about code structure. Do not use for pure security review, formatting-only review, performance profiling, or implementation tasks unless the user also asks for a code quality review.
15SKILL.mdUpdated May 29, 2026