TL;DR:
- Initialize GitHub Spec Kit with Qwen Code CLI
- Use automated formatting for conventional commits
- Adapt spec files for Qwen Code compatibility
- Maintain spec-driven development workflow
My Workflow Integration
Step 1: Initialize Spec Project
I start by initializing a GitHub Spec Kit project in my current directory, configured for Qwen Code CLI.
uvx --from git+https://github.com/github/spec-kit.git specify init --ai gemini --script sh --hereStep 2: Configure for Conventional Commits
I immediately set up automated formatting for conventional commits to maintain consistent commit history.
qwen -y -p "reformat all commits with rules from https://www.conventionalcommits.org/en/v1.0.0/#specification"Step 3: Configure QWEN Integration
After initialization, I rename the .gemini directory to .qwen for QWEN CLI compatibility.
mv .gemini .qwenThen I update any spec files that reference Gemini to work with Qwen Code:
qwen -y -p "find files in .specify that contains Gemini-related usage. Copy the syntax and adapt it for Qwen Code. Strictly edit the files, add the syntax, and don't do anything else"Step 4: Commit Changes
Finally, I commit the changes with proper conventional commit formatting:
qwen -y -p "commit the changes. Format this commit and going forward with rules from https://www.conventionalcommits.org/en/v1.0.0/#specification"Benefits of This Approach
This workflow provides several advantages:
- Consistency: All commits follow the conventional commits specification
- Automation: Qwen Code handles the formatting and adaptation automatically
- Compatibility: Properly configured for Qwen Code CLI usage
- Specification-Driven: Maintains the benefits of spec-driven development
By following this mantra, I ensure that all my projects start with a consistent, well-configured foundation that leverages both GitHub Spec Kit and Qwen Code CLI effectively.
