mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-12 02:37:45 +08:00

Files

catlog22 817f51c09f feat: Add Qwen CLI integration and update task commands

- Add Qwen CLI wrapper and commands for analyze and execute
- Update task create and execute documentation
- Enhance CLI tool integration capabilities

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-09-25 19:07:38 +08:00

3.1 KiB

Raw Blame History

name, description, usage, argument-hint, examples, model

name

description

usage

argument-hint

examples

model

analyze

Quick analysis of codebase patterns, architecture, and code quality using qwen CLI

/qwen:analyze <analysis-type>

analysis target or type

/qwen:analyze "React hooks patterns"

/qwen:analyze "authentication security"

/qwen:analyze "performance bottlenecks"

/qwen:analyze "API design patterns"

haiku

qwen Analysis Command (/qwen:analyze)

Overview

Quick analysis tool for codebase insights using intelligent pattern detection and template-driven analysis.

Core Guidelines: @~/.claude/workflows/intelligent-tools-strategy.md

Analysis Types

Type	Purpose	Example
pattern	Code pattern detection	"React hooks usage patterns"
architecture	System structure analysis	"component hierarchy structure"
security	Security vulnerabilities	"authentication vulnerabilities"
performance	Performance bottlenecks	"rendering performance issues"
quality	Code quality assessment	"testing coverage analysis"
dependencies	Third-party analysis	"outdated package dependencies"

Quick Usage

Basic Analysis

/qwen:analyze "authentication patterns"

Executes: qwen -p -a "@{**/*auth*} @{CLAUDE.md} $(template:analysis/pattern.txt)"

Targeted Analysis

/qwen:analyze "React component architecture"

Executes: qwen -p -a "@{src/components/**/*} @{CLAUDE.md} $(template:analysis/architecture.txt)"

Security Focus

/qwen:analyze "API security vulnerabilities"

Executes: qwen -p -a "@{**/api/**/*} @{CLAUDE.md} $(template:analysis/security.txt)"

Templates Used

Templates are automatically selected based on analysis type:

Pattern Analysis: ~/.claude/workflows/cli-templates/prompts/analysis/pattern.txt
Architecture Analysis: ~/.claude/workflows/cli-templates/prompts/analysis/architecture.txt
Security Analysis: ~/.claude/workflows/cli-templates/prompts/analysis/security.txt
Performance Analysis: ~/.claude/workflows/cli-templates/prompts/analysis/performance.txt

Workflow Integration

⚠️ Session Check: Automatically detects active workflow session via .workflow/.active-* marker file.

Analysis results saved to:

Active session: .workflow/WFS-[topic]/.chat/analysis-[timestamp].md
No session: Temporary analysis output

Common Patterns

Technology Stack Analysis

/qwen:analyze "project technology stack"
# Auto-detects: package.json, config files, dependencies

Code Quality Review

/qwen:analyze "code quality and standards"
# Auto-targets: source files, test files, CLAUDE.md

Migration Planning

/qwen:analyze "legacy code modernization"
# Focuses: older patterns, deprecated APIs, upgrade paths

Output Format

Analysis results include:

File References: Specific file:line locations
Code Examples: Relevant code snippets
Patterns Found: Common patterns and anti-patterns
Recommendations: Actionable improvements
Integration Points: How components connect

3.1 KiB Raw Blame History