feat(docs): add qwen-code skills, agents, and updated AGENTS.md (#3575)

- Add new skills: bugfix, feat-dev with structured workflows
- Update existing skills: docs-audit-and-refresh, docs-update-from-diff,
  e2e-testing, qwen-code-claw, structured-debugging, terminal-capture
- Update test-engineer agent with clearer constraints and formatting
- Update qc commands: bugfix, code-review, commit, create-issue, create-pr
- Reorganize .gitignore to keep qwen configs near top
- Expand AGENTS.md with development commands, feature/bugfix workflows,
  project directories table, and code review guidelines

Co-authored-by: 愚远 <zhenxing.tzx@alibaba-inc.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>

.qwen/commands/qc/bugfix.md

@@ -1,5 +1,6 @@
 ---
-description: Fix a bug from a GitHub issue, following the reproduce-first workflow
+description: Fix a bug from a GitHub issue, following the reproduce-first
+  workflow
 ---
 
 # Bugfix
@@ -12,8 +13,8 @@ A GitHub issue URL or number: $ARGUMENTS
 
 ### 1. Read the issue and create the issue file
 
-Create `.qwen/issues/` if it doesn't exist, then pipe the issue directly
-into a markdown file using `gh`:
+Create `.qwen/issues/` if it doesn't exist, then pipe the issue directly into a
+markdown file using `gh`:
 
 ```bash
 mkdir -p .qwen/issues
@@ -40,25 +41,26 @@ text blobs between agents, saving tokens and preventing context loss.
 
 ### 2. Reproduce
 
-Spawn the `test-engineer` agent and tell it to read `.qwen/issues/issue-<number>.md`
-for the issue details, then assess and reproduce the bug. Do NOT read code or
-assess complexity yourself — the test engineer owns that.
+Spawn the `test-engineer` agent and tell it to read
+`.qwen/issues/issue-<number>.md` for the issue details, then assess and
+reproduce the bug. Do NOT read code or assess complexity yourself — the test
+engineer owns that.
 
-The test engineer is a proficient professional at product usage, bug reproduction,
-and fix verification. Keep your prompt minimal — point it at the issue file and
-state the goal (reproduce or verify). Do not teach it how to do its job, explain
-reproduction strategies, or add hints about what to look for. It will figure that
-out on its own.
+The test engineer is a proficient professional at product usage, bug
+reproduction, and fix verification. Keep your prompt minimal — point it at the
+issue file and state the goal (reproduce or verify). Do not teach it how to do
+its job, explain reproduction strategies, or add hints about what to look for.
+It will figure that out on its own.
 
-Wait for the test engineer to finish. Then **read `.qwen/issues/issue-<number>.md`**
-to get the reproduction report. If the status is `NOT_REPRODUCED`, say so and
-stop.
+Wait for the test engineer to finish. Then **read
+`.qwen/issues/issue-<number>.md`** to get the reproduction report. If the status
+is `NOT_REPRODUCED`, say so and stop.
 
 ### 3. Locate and fix
 
-Read the relevant code and make the fix. Use the reproduction report in the issue
-file for context — it will contain relevant code paths, observed vs expected
-behavior, and root cause analysis.
+Read the relevant code and make the fix. Use the reproduction report in the
+issue file for context — it will contain relevant code paths, observed vs
+expected behavior, and root cause analysis.
 
 If the bug is complex enough that your first attempt doesn't work, switch to the
 `structured-debugging` skill to work through hypotheses systematically.
@@ -67,9 +69,9 @@ If the bug is complex enough that your first attempt doesn't work, switch to the
 
 Build your changes (`npm run build && npm run bundle`), then spawn the
 `test-engineer` agent again and tell it to read `.qwen/issues/issue-<number>.md`
-and _verify_ the fix. It will re-run its reproduction steps using
-`node dist/cli.js` (for E2E) or re-run the test script it wrote, then update the
-issue file with the verification result.
+and _verify_ the fix. It will re-run its reproduction steps using `node
+dist/cli.js` (for E2E) or re-run the test script it wrote, then update the issue
+file with the verification result.
 
 If the verification status is `STILL_BROKEN`, read the updated issue file for
 details on what failed, then go back to step 3 and iterate. Use the
@@ -79,7 +81,7 @@ until verification returns `VERIFIED_FIXED`.
 ### 5. Tests
 
 Run the unit tests for any packages you modified. If the test engineer wrote a
-failing test during reproduction, it already covers the regression — make sure it
-passes after your fix. Otherwise, add a test (unit or integration) that covers
-the failure scenario from the issue so a future regression gets caught
+failing test during reproduction, it already covers the regression — make sure
+it passes after your fix. Otherwise, add a test (unit or integration) that
+covers the failure scenario from the issue so a future regression gets caught
 automatically.