@jaydennleemc/qwen-code-local 0.12.6 → 0.13.1

package/README.md

@@ -125,11 +125,11 @@ Use this if you want more flexibility over which provider and model to use. Supp
 - **Anthropic**: Claude models
 - **Google GenAI**: Gemini models
 
-The **recommended** way to configure models and providers is by editing `~/.qwen_local/settings.json` (create it if it doesn't exist). This file lets you define all available models, API keys, and default settings in one place.
+The **recommended** way to configure models and providers is by editing `~/.qwen/settings.json` (create it if it doesn't exist). This file lets you define all available models, API keys, and default settings in one place.
 
 ##### Quick Setup in 3 Steps
 
-**Step 1:** Create or edit `~/.qwen_local/settings.json`
+**Step 1:** Create or edit `~/.qwen/settings.json`
 
 Here is a complete example:
 
@@ -349,7 +349,7 @@ Use the `/model` command at any time to switch between all configured models.
 
 > **Tip:** You can also set API keys via `export` in your shell or `.env` files, which take higher priority than `settings.json` → `env`. See the [authentication guide](https://qwenlm.github.io/qwen-code-docs/en/users/configuration/auth/) for full details.
 
-> **Security note:** Never commit API keys to version control. The `~/.qwen_local/settings.json` file is in your home directory and should stay private.
+> **Security note:** Never commit API keys to version control. The `~/.qwen/settings.json` file is in your home directory and should stay private.
 
 ## Usage
 
@@ -417,10 +417,10 @@ Build on top of Qwen Code with the TypeScript SDK:
 
 Qwen Code can be configured via `settings.json`, environment variables, and CLI flags.
 
-| File                          | Scope         | Description                                                                             |
-| ----------------------------- | ------------- | --------------------------------------------------------------------------------------- |
-| `~/.qwen_local/settings.json` | User (global) | Applies to all your Qwen Code sessions. **Recommended for `modelProviders` and `env`.** |
-| `.qwen/settings.json`         | Project       | Applies only when running Qwen Code in this project. Overrides user settings.           |
+| File                    | Scope         | Description                                                                             |
+| ----------------------- | ------------- | --------------------------------------------------------------------------------------- |
+| `~/.qwen/settings.json` | User (global) | Applies to all your Qwen Code sessions. **Recommended for `modelProviders` and `env`.** |
+| `.qwen/settings.json`   | Project       | Applies only when running Qwen Code in this project. Overrides user settings.           |
 
 The most commonly used top-level fields in `settings.json`:
 
@@ -457,7 +457,7 @@ To report a bug from within the CLI, run `/bug` and include a short title and re
 
 ## Connect with Us
 
-- Discord: https://discord.gg/ycKBjdNd
+- Discord: https://discord.gg/RN7tqZCeDK
 - Dingtalk: https://qr.dingtalk.com/action/joingroup?code=v1,k1,+FX6Gf/ZDlTahTIRi8AEQhIaBlqykA0j+eBKKdhLeAE=&_dt_no_comment=1&origin=1
 
 ## Acknowledgments

package/dist/bundled/review/SKILL.md

@@ -15,15 +15,16 @@ You are an expert code reviewer. Your job is to review code changes and provide
 
 ## Step 1: Determine what to review
 
-Based on the arguments provided:
+Your goal here is to understand the scope of changes so you can dispatch agents effectively in Step 2. Based on the arguments provided:
 
 - **No arguments**: Review local uncommitted changes
   - Run `git diff` and `git diff --staged` to get all changes
   - If both diffs are empty, inform the user there are no changes to review and stop here — do not proceed to the review agents
 
 - **PR number or URL** (e.g., `123` or `https://github.com/.../pull/123`):
-  - Run `gh pr view <number>` to get PR details
-  - Run `gh pr diff <number>` to get the diff
+  - Save the current branch name, stash any local changes (`git stash --include-untracked`), then `gh pr checkout <number>`
+  - Run `gh pr view <number>` and save the output (title, description, base branch, etc.) to a temp file (e.g., `/tmp/pr-review-context.md`) so agents can read it without you repeating it in each prompt
+  - Note the base branch (e.g., `main`) — agents will use `git diff <base>...HEAD` to get the diff and can read files directly
 
 - **File path** (e.g., `src/foo.ts`):
   - Run `git diff HEAD -- <file>` to get recent changes
@@ -33,6 +34,8 @@ Based on the arguments provided:
 
 Launch **four parallel review agents** to analyze the changes from different angles. Each agent should focus exclusively on its dimension.
 
+**IMPORTANT**: Do NOT paste the full diff into each agent's prompt — this duplicates it 4x. Instead, give each agent the command to obtain the diff, a concise summary of what the changes are about, and its review focus. Each agent can read files and search the codebase on its own.
+
 ### Agent 1: Correctness & Security
 
 Focus areas:
@@ -77,9 +80,11 @@ Focus areas:
 - Unexpected side effects or hidden coupling
 - Anything else that looks off — trust your instincts
 
-## Step 3: Aggregate and present findings
+## Step 3: Restore environment and present findings
+
+If you checked out a PR branch in Step 1, restore the original state first: check out the original branch, `git stash pop` if changes were stashed, and remove the temp file.
 
-Combine results from all four agents into a single, well-organized review. Use this format:
+Then combine results from all four agents into a single, well-organized review. Use this format:
 
 ### Summary