feat: add Qwen Code support to Spec Kit#182
Conversation
Add comprehensive Qwen Code integration following existing patterns: - Add Qwen as fourth AI assistant option in CLI - Update all documentation to include Qwen CLI references - Extend GitHub Actions workflow for Qwen template generation - Add Qwen support to shell scripts and templates - Maintain backward compatibility with existing assistants
|
Truly appreciated |
Resolved conflicts in release workflow and CLI: - Integrated external script approach for release package creation - Added Qwen Code support to release script and CLI tool checking - Maintained all existing functionality for other AI assistants
- Change from commands/ to .qwen/commands/ directory - Match official PR github#182 implementation - Fix command recognition in Qwen CLI
|
Can't wait to get qwen code support as well |
Combines Qwen Code support with new script variant structure from main. Key additions: - Qwen Code AI assistant support - PowerShell script variants alongside Bash - Updated release packaging for per-script variants - Maintains all existing Cursor support from main Co-authored-by: Claude <noreply@anthropic.com>
|
@ahmet-cetinkaya is this complete? |
|
@vjaykrsna There’s a small mistake in your command — when specifying a branch, you should use uvx --from git+https://github.com/ahmet-cetinkaya/spec-kit@feature/add-qwen-support specifyThis will let you see the new option. However, since spec-kit fetches its templates from releases, the tool won’t fully work this way. git clone https://github.com/ahmet-cetinkaya/spec-kit -b feature/add-qwen-support
cd spec-kit
uv sync
uv run specify |
|
by default it fetch from github had to modify the function to get it to work after generating the files manually |
|
@ahmet-cetinkaya once you address the nit changes I highlighted, I am happy to merge this. |
|
Hi @localden, The requested changes are applied, and the branch is now ready to merge. Appreciate the review! 🚀 I usually keep lists numbered sequentially so they’re easier to read in raw Markdown, but if the |
|
@ahmet-cetinkaya - last request, can you rev the CLI version and update the changelog with the addition of Qwen support? |
Add entry for Qwen Code support as new AI assistant option
|
@localden I've addressed your last request:
The changes have been pushed to the branch. This should be ready to merge now. |
|
Waiting for the PR to merge feels like forever. |
|
Thank you for contribution, @ahmet-cetinkaya! 🥳 |
|
hey @ahmet-cetinkaya, @localden there are some missing definitions to support qwen, please check my pr: #64 Important ones are update-agent-context scripts, create-release-packages.sh, release.yml as far as I can see. |
|
I tried this moments ago, didn't work. uvx --from git+https://github.com/github/spec-kit.git specify init spec-sample I did a search for the missing zip file in the merged repo, didn't find it. We can uhh select qwen tho, at least. Tried it like this also, same error. uvx --from git+https://github.com/github/spec-kit.git specify init spec-qwen --ai qwen --script sh |
|
@aemr3 @SeanPtest - Fixed! PR #321 adds missing Qwen assets to releases. specify init --ai qwen will work after merge. Thanks! |
|
#330 Changed md to toml so that the |
…upport feat: add Qwen Code support to Spec Kit
Summary
Changes Made
src/specify_cli/__init__.pywith proper help text and tool checkingscripts/update-agent-context.shto support QWEN.md generation.qwen/commands/*.mdstructureTesting
--ai claude, gemini, copilot, or qwenImplementation Details
.qwen/commands/*.mdformatQWEN.mdin project rootqwencommand availabilityhttps://github.com/QwenLM/qwen-codeThis extends Spec Kit's AI assistant ecosystem to include Qwen while maintaining full compatibility with existing workflows.