mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-04-28 03:30:40 +00:00
202be6ec7d
Some checks are pending
Qwen Code CI / Lint (push) Waiting to run
Qwen Code CI / Test (push) Blocked by required conditions
Qwen Code CI / Test-1 (push) Blocked by required conditions
Qwen Code CI / Test-2 (push) Blocked by required conditions
Qwen Code CI / Test-3 (push) Blocked by required conditions
Qwen Code CI / Test-4 (push) Blocked by required conditions
Qwen Code CI / Test-5 (push) Blocked by required conditions
Qwen Code CI / Test-6 (push) Blocked by required conditions
Qwen Code CI / Test-7 (push) Blocked by required conditions
Qwen Code CI / Test-8 (push) Blocked by required conditions
Qwen Code CI / Post Coverage Comment (push) Blocked by required conditions
Qwen Code CI / CodeQL (push) Waiting to run
E2E Tests / E2E Test (Linux) - sandbox:none (push) Waiting to run
E2E Tests / E2E Test (Linux) - sandbox:docker (push) Waiting to run
E2E Tests / E2E Test - macOS (push) Waiting to run
* feat(vscode): expose /skills as slash command with secondary picker Add a secondary completion picker for the /skills slash command in the VSCode IDE companion, allowing users to browse and select skills from a dropdown before sending. Changes: - CLI: add 'skills' to ALLOWED_BUILTIN_COMMANDS_NON_INTERACTIVE whitelist - CLI: send available_skills_update via ACP with skill names/descriptions - Extension: handle available_skills_update in session update handler - Webview: implement secondary picker that triggers after selecting /skills - Webview: allow spaces in completion trigger for /skills sub-queries Closes #1562 Made-with: Cursor * feat(vscode-ide-companion): embed skills in commands update metadata - Move available skills from separate session update to _meta field of available_commands_update for more efficient delivery - Simplify skill data to just skill names (string array) - Add skillsCompletion utility for secondary picker logic - Cache available skills in WebViewProvider for replay on webview ready - Update all related types and handlers to support the new structure Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> * refactor(vscode-ide-companion): simplify skills picker flow * refactor(vscode-ide-companion): extract skills completion utils to shared module Move `isSkillsSecondaryQuery`, `shouldOpenSkillsSecondaryPicker`, and `SKILL_ITEM_ID_PREFIX` from App.tsx and useCompletionTrigger.ts into a shared `completionUtils.ts` file to eliminate duplication. * fix(vscode-ide-companion): restore skills picker state on reload Cache and replay available skills when the webview becomes ready again. Clear stale skills when commands metadata does not include availableSkills. * fix(vscode-ide-companion): replay slash commands after webview reload Cache available commands in the webview provider. Replay them on webviewReady so slash command state survives reloads. * fix(vscode-ide-companion): import AvailableCommand from ACP SDK * fix(vscode-ide-companion): fallback /skills to direct command * test(vscode-ide-companion): cover skills secondary picker flow * test(vscode-ide-companion): guard App mock initialization * fix(vscode-ide-companion): remove duplicate AvailableCommand import The auto-merge introduced a duplicate AvailableCommand in the @agentclientprotocol/sdk import block, causing TS2300. * fix(vscode-ide-companion): remove duplicate availableCommands replay in handleWebviewReady The handleWebviewReady method was sending cachedAvailableCommands twice on every webview-ready handshake, causing an unnecessary extra state update in the webview. --------- Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
49 lines
1.2 KiB
Markdown
49 lines
1.2 KiB
Markdown
---
|
|
description: Create a pull request based on staged code changes
|
|
---
|
|
|
|
# Create PR
|
|
|
|
## Overview
|
|
|
|
Create a well-structured pull request with proper description and title.
|
|
|
|
## Steps
|
|
|
|
1. **Review staged changes**
|
|
|
|
- Review all staged changes to understand what has been done
|
|
- Do not touch unstaged changes
|
|
|
|
2. **Prepare branch**
|
|
|
|
- Create a new branch with proper name if current branch is main
|
|
- Ensure all changes are committed
|
|
- Push branch to remote
|
|
|
|
3. **Write PR description**
|
|
|
|
- Use PR Template below
|
|
- Summarize changes clearly
|
|
- Include context and motivation
|
|
- List any breaking changes
|
|
- Link related issues if provided, or use "No linked issues"
|
|
- Leave the "Screenshots / Video Demo" section empty for the author to fill in
|
|
manually
|
|
- Add this line at the end of PR body: "🤖 Generated with [Qwen
|
|
Code](https://github.com/QwenLM/qwen-code)", with a line separator
|
|
|
|
4. **Set up PR**
|
|
|
|
- Create PR title and body
|
|
- Submit PR with gh command
|
|
- **If a GitHub token is provided in the user's message**, use it by setting
|
|
the `GH_TOKEN` environment variable:
|
|
```bash
|
|
GH_TOKEN=<provided_token> gh pr create --title "..." --body "..."
|
|
```
|
|
- If no token is provided, use the default `gh` authentication
|
|
|
|
## PR Template
|
|
|
|
@{.github/pull_request_template.md}
|