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/commit.md

@@ -6,16 +6,17 @@ description: Commit staged changes with an AI-generated commit message and push
 
 ## Overview
 
-Generate a clear, concise commit message based on staged changes, confirm with the user, then commit and push.
+Generate a clear, concise commit message based on staged changes, confirm with
+the user, then commit and push.
 
 ## Steps
 
 ### 1. Check repository status
 
 - Run `git status` to check:
-  - Are there any staged changes?
-  - Are there unstaged changes?
-  - What is the current branch?
+- Are there any staged changes?
+- Are there unstaged changes?
+- What is the current branch?
 
 ### 2. Handle unstaged changes
 
@@ -27,32 +28,34 @@ Generate a clear, concise commit message based on staged changes, confirm with t
 
 - Run `git diff --staged` to see all staged changes
 - Analyze the changes in depth to understand:
-  - What files were modified/added/deleted
-  - The nature of the changes (feature, fix, refactor, docs, etc.)
-  - The scope and impact of the changes
+- What files were modified/added/deleted
+- The nature of the changes (feature, fix, refactor, docs, etc.)
+- The scope and impact of the changes
 
 ### 4. Handle branch logic
 
 - Get current branch name with `git branch --show-current`
 - **If current branch is `main` or `master`:**
-  - Generate a proper branch name based on the changes
-  - Create and switch to the new branch: `git checkout -b <branch-name>`
+- Generate a proper branch name based on the changes
+- Create and switch to the new branch: `git checkout -b <branch-name>`
 - **If current branch is NOT main/master:**
-  - Check if branch name matches the staged changes
-  - If branch name doesn't match changes, ask user:
+- Check if branch name matches the staged changes
+- If branch name doesn't match changes, ask user:
     - "Current branch `<branch>` doesn't seem to match these changes."
-    - "Options: (1) Create and switch to a new branch, (2) Commit directly on current branch"
+    - "Options: (1) Create a new branch, (2) Commit on current branch"
     - Wait for user decision
 
 ### 5. Generate commit message
 
 - Types: feat, fix, docs, style, refactor, test, chore
 - Guidelines:
-  - Be clear and concise
-  - Reference issues if mentioned in changes
-  - Include scope in parentheses when applicable (e.g., `fix(insight):`, `feat(auth):`)
-  - Add bullet points for detailed changes if it addes more value, otherwise do not use bullets
-  - Include a footer explaining the purpose/impact of the changes
+- Be clear and concise
+- Reference issues if mentioned in changes
+- Include scope in parentheses when applicable (e.g., `fix(insight):`,
+  `feat(auth):`)
+- Add bullet points for detailed changes if it addes more value, otherwise do
+  not use bullets
+- Include a footer explaining the purpose/impact of the changes
 
 **Format:**
 
@@ -75,5 +78,5 @@ This <explains the why/impact of the changes>.
 ### 7. Commit and push
 
 - After user confirms:
-  - `git commit -m "<commit-message>"`
-  - `git push -u origin <branch-name>` (use `-u` for new branches)
+- `git commit -m "<commit-message>"`
+- `git push -u origin <branch-name>` (use `-u` for new branches)