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/create-issue.md

@@ -6,39 +6,41 @@ description: Draft and submit a GitHub issue based on a user-provided idea
 
 ## Overview
 
-Take the user's idea or bug description, investigate the codebase to understand the full context, draft a GitHub issue for review, and submit it once approved.
+Take the user's idea or bug description, investigate the codebase to understand
+the full context, draft a GitHub issue for review, and submit it once approved.
 
 ## Input
 
-The user provides a brief description of a feature request or bug report: {{args}}
+The user provides a brief description of a feature request or bug report:
+{{args}}
 
 ## Steps
 
-1. **Understand the request**
-   - Read the user's description carefully
-   - Determine whether this is a feature request or a bug report
+1.  **Understand the request**
+- Read the user's description carefully
+- Determine whether this is a feature request or a bug report
 
-2. **Investigate the codebase**
-   - Search for relevant code, files, and existing behavior related to the request
-   - Build a thorough understanding of how the current system works
-   - Identify any related issues or prior art if mentioned
+2.  **Investigate the codebase**
+- Search for relevant code, files, and existing behavior related to the request
+- Build a thorough understanding of how the current system works
+- Identify any related issues or prior art if mentioned
 
-3. **Draft the issue**
-   - Write a markdown file for the user to review
-   - Use the appropriate template:
+3.  **Draft the issue**
+- Write a markdown file for the user to review
+- Use the appropriate template:
      - Feature request: follow @.github/ISSUE_TEMPLATE/feature_request.yml
      - Bug report: follow @.github/ISSUE_TEMPLATE/bug_report.yml
-   - Write from the user's perspective, not as an implementation spec
-   - Keep the language clear and concise, AVOID internal implementation details
+- Write from the user's perspective, not as an implementation spec
+- Keep the language clear and concise, AVOID internal implementation details
 
-4. **Review with user**
-   - Present the draft file to the user
-   - Iterate on feedback until the user is satisfied
-   - Do NOT submit until the user explicitly asks to
+4.  **Review with user**
+- Present the draft file to the user
+- Iterate on feedback until the user is satisfied
+- Do NOT submit until the user explicitly asks to
 
-5. **Submit the issue**
-   - When the user confirms, create the issue using `gh issue create`
-   - Apply the appropriate labels:
+5.  **Submit the issue**
+- When the user confirms, create the issue using `gh issue create`
+- Apply the appropriate labels:
      - Feature request: `type/feature-request`, `status/needs-triage`
      - Bug report: `type/bug`, `status/needs-triage`
-   - Report back the issue URL
+- Report back the issue URL