From de60f9ee7f9952f3afe52a5004039afb05ccd5b4 Mon Sep 17 00:00:00 2001
From: Jeffery <jiantw83@yahoo.com>
Date: Sat, 16 May 2026 16:07:37 +0000
Subject: [PATCH 1/2] chore: update release workflows

---
 .gitea/workflows/master.yaml |  2 +-
 .gitea/workflows/review.yaml |  4 ++++
 action.yml                   | 14 +++++++-------
 3 files changed, 12 insertions(+), 8 deletions(-)

diff --git a/.gitea/workflows/master.yaml b/.gitea/workflows/master.yaml
index 1be7a87..b37b091 100644
--- a/.gitea/workflows/master.yaml
+++ b/.gitea/workflows/master.yaml
@@ -21,7 +21,7 @@ jobs:
     - name: 發布專案
       uses: akkuman/gitea-release-action@${{ vars.ACTION_RELEASE_VERSION }}
       with:
-        tag_name: "v${{ needs.version.outputs.version }}"
+        tag_name: v${{ needs.version.outputs.version }}
     - name: 清理成品
       uses: https://gitea.jsc.idv.tw/actions/cleanup-release@${{ vars.ACTION_CLEANUP_RELEASE_VERSION }}
       with:
diff --git a/.gitea/workflows/review.yaml b/.gitea/workflows/review.yaml
index a24c7be..b81ac76 100644
--- a/.gitea/workflows/review.yaml
+++ b/.gitea/workflows/review.yaml
@@ -1,6 +1,8 @@
 name: AI
 on:
   pull_request:
+    branches-ignore:
+      - master
     types: [opened, synchronize]
 jobs:
   code-review:
@@ -10,6 +12,8 @@ jobs:
     - name: AI Code Review
       uses: https://gitea.jsc.idv.tw/actions/code-review@${{ vars.ACTION_CODE_REVIEW_VERSION }}
       with:
+        GITEA_TOKEN: ${{ secrets.RUNNER_TOKEN }}
+        GITEA_COMMENT_TOKEN: ${{ secrets.GITEA_TOKEN }}
         GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }},${{ secrets.GEMINI_API_KEY_1 }},${{ secrets.GEMINI_API_KEY_2 }},${{ secrets.GEMINI_API_KEY_3 }},${{ secrets.GEMINI_API_KEY_4 }},${{ secrets.GEMINI_API_KEY_5 }},${{ secrets.GEMINI_API_KEY_6 }},${{ secrets.GEMINI_API_KEY_7 }},${{ secrets.GEMINI_API_KEY_8 }},${{ secrets.GEMINI_API_KEY_9 }},${{ secrets.GEMINI_API_KEY_10 }},${{ secrets.GEMINI_API_KEY_11 }},${{ secrets.GEMINI_API_KEY_12 }},${{ secrets.GEMINI_API_KEY_13 }},${{ secrets.GEMINI_API_KEY_14 }},${{ secrets.GEMINI_API_KEY_15 }},${{ secrets.GEMINI_API_KEY_16 }},${{ secrets.GEMINI_API_KEY_17 }},${{ secrets.GEMINI_API_KEY_18 }},${{ secrets.GEMINI_API_KEY_19 }}
         GEMINI_BASE_URL: https://generativelanguage.googleapis.com/v1beta
         GEMINI_MODEL: ${{ vars.GEMINI_MODEL }}
diff --git a/action.yml b/action.yml
index 8c6351e..cbb72b3 100644
--- a/action.yml
+++ b/action.yml
@@ -15,21 +15,21 @@ runs:
   using: 'composite'
   steps:
   - name: 壓縮套件
-    uses: https://gitea.jsc.idv.tw/actions/zip@v0.0.6
+    uses: https://gitea.jsc.idv.tw/actions/zip@v0.0.7
     with:
       RELEASE_VERSION: ${{ inputs.RELEASE_VERSION }}
   - name: 發布套件
     uses: akkuman/gitea-release-action@v1
     with:
-      name: "${{ inputs.PROJECT_NAME }} v${{ inputs.RELEASE_VERSION }}"
-      tag_name: "v${{ inputs.RELEASE_VERSION }}"
+      name: ${{ inputs.PROJECT_NAME }} v${{ inputs.RELEASE_VERSION }}
+      tag_name: v${{ inputs.RELEASE_VERSION }}
       target_commitish: master
       files: |
         ${{ inputs.PROJECT_NAME }}.${{ inputs.RELEASE_VERSION }}.zip
   - name: 推送套件
-    uses: https://gitea.jsc.idv.tw/actions/nuget-push@v0.1.6
+    uses: https://gitea.jsc.idv.tw/actions/nuget-push@v0.1.7
     with:
-      RELEASE_VERSION: "${{ inputs.RELEASE_VERSION }}"
-      RUNNER_TOKEN: "${{ inputs.RUNNER_TOKEN }}"
+      RELEASE_VERSION: ${{ inputs.RELEASE_VERSION }}
+      RUNNER_TOKEN: ${{ inputs.RUNNER_TOKEN }}
   - name: 清理發布
-    uses: https://gitea.jsc.idv.tw/actions/cleanup-release@v0.4.1
\ No newline at end of file
+    uses: https://gitea.jsc.idv.tw/actions/cleanup-release@v0.4.2
\ No newline at end of file

From aea78bc436ffde219fc83e0a1528bdaba6ee20c8 Mon Sep 17 00:00:00 2001
From: AI Review Bot <ai-review[bot]@gitea>
Date: Sat, 16 May 2026 16:09:32 +0000
Subject: [PATCH 2/2] chore: update ai-review findings [ai-review-bot][success]

---
 .amazonq/rules/triage-findings.md             | 14 ++++++
 .claude/skills/triage-findings/SKILL.md       | 29 ++++++++++++
 .codex/skills/triage-findings/SKILL.md        | 45 +++++++++++++++++++
 .../skills/triage-findings/agents/openai.yaml |  4 ++
 .gemini/skills/triage-findings/SKILL.md       | 29 ++++++++++++
 .gitea/ai-review/findings.json                |  1 +
 .github/copilot-instructions.md               | 14 ++++++
 .github/skills/triage-findings/SKILL.md       | 14 ++++++
 CLAUDE.md                                     | 16 +++++++
 GEMINI.md                                     | 14 ++++++
 10 files changed, 180 insertions(+)
 create mode 100644 .amazonq/rules/triage-findings.md
 create mode 100644 .claude/skills/triage-findings/SKILL.md
 create mode 100644 .codex/skills/triage-findings/SKILL.md
 create mode 100644 .codex/skills/triage-findings/agents/openai.yaml
 create mode 100644 .gemini/skills/triage-findings/SKILL.md
 create mode 100644 .gitea/ai-review/findings.json
 create mode 100644 .github/copilot-instructions.md
 create mode 100644 .github/skills/triage-findings/SKILL.md
 create mode 100644 CLAUDE.md
 create mode 100644 GEMINI.md

diff --git a/.amazonq/rules/triage-findings.md b/.amazonq/rules/triage-findings.md
new file mode 100644
index 0000000..4b65ce1
--- /dev/null
+++ b/.amazonq/rules/triage-findings.md
@@ -0,0 +1,14 @@
+# Triage Findings
+
+When the task is to triage review findings, follow this workflow:
+
+1. Merge all findings into one list.
+2. Remove duplicates.
+3. Sort by severity: `critical` -> `warning` -> `info`.
+4. Renumber from 1 after sorting.
+5. Fix real issues with the smallest safe change.
+6. Add false positives to `.gitea/ai-review/exclusions.json`, preserving the original wording, language, and semantics as much as possible.
+7. Add or update tests when behavior changes.
+8. Re-check the issue after each fix.
+
+Use the repo-local `triage-findings` skill for the same workflow when running in Codex.
diff --git a/.claude/skills/triage-findings/SKILL.md b/.claude/skills/triage-findings/SKILL.md
new file mode 100644
index 0000000..c4ab450
--- /dev/null
+++ b/.claude/skills/triage-findings/SKILL.md
@@ -0,0 +1,29 @@
+---
+name: triage-findings
+description: Triage findings, fix real issues, and exclude false positives.
+---
+
+# Triage Findings
+
+## Use
+
+直接輸入：`triage-findings 問題原始檔(文字或截圖)`
+
+## Workflow
+
+1. Merge all findings.
+2. Sort by severity:
+   - critical
+   - warning
+   - info
+3. Renumber from 1.
+4. Fix real issues.
+5. Put false positives into `.gitea/ai-review/exclusions.json`, preserving the original wording, language, and semantics as much as possible.
+6. Add tests when behavior changes.
+
+## Output Rules
+
+- Keep the final list short.
+- Keep numbering contiguous.
+- Preserve file path, location, and fix.
+- When writing exclusions, prefer the original issue text over paraphrased rewrites.
diff --git a/.codex/skills/triage-findings/SKILL.md b/.codex/skills/triage-findings/SKILL.md
new file mode 100644
index 0000000..21476cb
--- /dev/null
+++ b/.codex/skills/triage-findings/SKILL.md
@@ -0,0 +1,45 @@
+---
+name: triage-findings
+description: Merge code-review findings, sort and renumber them by severity, resolve real issues, and move false positives into exclusions.
+---
+
+# Triage Findings
+
+## When To Use
+
+Use this skill when you receive multiple review findings, screenshots, comments, or issue lists that need to become one final triaged list.
+It is also used when some findings are false positives and should be moved into the exclusions list.
+
+## Workflow
+
+1. Collect all findings into one list.
+2. Merge duplicates into a single finding when they describe the same issue.
+3. Sort the final list by severity:
+   - critical
+   - warning
+   - info
+4. Renumber the sorted list from 1 upward.
+5. Rewrite each finding concisely so the final list reads cleanly and consistently.
+6. If a finding is a false positive, do not keep it in the final list.
+7. Add false positives to the exclusions list using the existing schema in the repo or task context, and preserve the original finding wording as much as possible, including language and semantics.
+
+## Resolution Flow
+
+After the list is merged and ordered, resolve the remaining findings one by one.
+
+1. Start from the highest severity item.
+2. Identify the root cause in the relevant file or context.
+3. Apply the smallest safe change that fixes the issue.
+4. Add or update tests when behavior changes.
+5. Re-check the issue after the change.
+6. If the item is confirmed false positive, move it to exclusions instead of changing code.
+7. Continue until the list is either fixed or explicitly excluded.
+
+## Output Rules
+
+- Keep the final findings list in severity order, then by any stable secondary order needed to make it readable.
+- Keep numbering contiguous after filtering and merging.
+- Preserve useful details like file path, location, and suggested fix.
+- Keep exclusions entries minimal and consistent with the project schema.
+- When writing exclusions, prefer the original issue text and language; only paraphrase if needed to fit the schema.
+- If the source already provides a severity or title, keep it unless it conflicts with the final ordering.
diff --git a/.codex/skills/triage-findings/agents/openai.yaml b/.codex/skills/triage-findings/agents/openai.yaml
new file mode 100644
index 0000000..6f59e2c
--- /dev/null
+++ b/.codex/skills/triage-findings/agents/openai.yaml
@@ -0,0 +1,4 @@
+interface:
+  display_name: "Triage Findings"
+  short_description: "Triage, sort, fix, and exclude review findings"
+  default_prompt: "Use $triage-findings to merge review findings, sort and renumber them by severity, resolve real issues one by one, and add false positives to exclusions."
diff --git a/.gemini/skills/triage-findings/SKILL.md b/.gemini/skills/triage-findings/SKILL.md
new file mode 100644
index 0000000..c4ab450
--- /dev/null
+++ b/.gemini/skills/triage-findings/SKILL.md
@@ -0,0 +1,29 @@
+---
+name: triage-findings
+description: Triage findings, fix real issues, and exclude false positives.
+---
+
+# Triage Findings
+
+## Use
+
+直接輸入：`triage-findings 問題原始檔(文字或截圖)`
+
+## Workflow
+
+1. Merge all findings.
+2. Sort by severity:
+   - critical
+   - warning
+   - info
+3. Renumber from 1.
+4. Fix real issues.
+5. Put false positives into `.gitea/ai-review/exclusions.json`, preserving the original wording, language, and semantics as much as possible.
+6. Add tests when behavior changes.
+
+## Output Rules
+
+- Keep the final list short.
+- Keep numbering contiguous.
+- Preserve file path, location, and fix.
+- When writing exclusions, prefer the original issue text over paraphrased rewrites.
diff --git a/.gitea/ai-review/findings.json b/.gitea/ai-review/findings.json
new file mode 100644
index 0000000..fe51488
--- /dev/null
+++ b/.gitea/ai-review/findings.json
@@ -0,0 +1 @@
+[]
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
new file mode 100644
index 0000000..f1a77ef
--- /dev/null
+++ b/.github/copilot-instructions.md
@@ -0,0 +1,14 @@
+# Triage Findings
+
+Use the triage-finding workflow for review issue lists:
+
+1. Merge findings into one list.
+2. Remove duplicates.
+3. Sort by severity: `critical` -> `warning` -> `info`.
+4. Renumber from 1.
+5. Fix real issues with the smallest safe change.
+6. Put false positives into `.gitea/ai-review/exclusions.json`, preserving the original wording, language, and semantics as much as possible.
+7. Add or update tests when behavior changes.
+8. Re-check after each fix.
+
+The full reusable skill lives in `.claude/skills/triage-findings/SKILL.md`.
diff --git a/.github/skills/triage-findings/SKILL.md b/.github/skills/triage-findings/SKILL.md
new file mode 100644
index 0000000..8ca4117
--- /dev/null
+++ b/.github/skills/triage-findings/SKILL.md
@@ -0,0 +1,14 @@
+# Triage Findings
+
+Use the triage-finding workflow for review issue lists:
+
+1. Merge findings into one list.
+2. Remove duplicates.
+3. Sort by severity: `critical` -> `warning` -> `info`.
+4. Renumber from 1.
+5. Fix real issues with the smallest safe change.
+6. Put false positives into `.gitea/ai-review/exclusions.json`, preserving the original wording, language, and semantics as much as possible.
+7. Add or update tests when behavior changes.
+8. Re-check after each fix.
+
+The reusable skill lives in `.gemini/skills/triage-findings/SKILL.md`.
diff --git a/CLAUDE.md b/CLAUDE.md
new file mode 100644
index 0000000..fa2403d
--- /dev/null
+++ b/CLAUDE.md
@@ -0,0 +1,16 @@
+# Triage Findings
+
+When the task is to triage review findings, follow this workflow:
+
+1. Merge all findings into one list.
+2. Remove duplicates.
+3. Sort by severity: `critical` -> `warning` -> `info`.
+4. Renumber from 1 after sorting.
+5. Fix real issues with the smallest safe change.
+6. Add false positives to `.gitea/ai-review/exclusions.json`, preserving the original wording, language, and semantics as much as possible.
+7. Add or update tests when behavior changes.
+8. Re-check the issue after each fix.
+
+Use the repo-local `triage-findings` skill for the same workflow when running in Codex.
+
+Trigger it with `/triage-findings`.
diff --git a/GEMINI.md b/GEMINI.md
new file mode 100644
index 0000000..8ca4117
--- /dev/null
+++ b/GEMINI.md
@@ -0,0 +1,14 @@
+# Triage Findings
+
+Use the triage-finding workflow for review issue lists:
+
+1. Merge findings into one list.
+2. Remove duplicates.
+3. Sort by severity: `critical` -> `warning` -> `info`.
+4. Renumber from 1.
+5. Fix real issues with the smallest safe change.
+6. Put false positives into `.gitea/ai-review/exclusions.json`, preserving the original wording, language, and semantics as much as possible.
+7. Add or update tests when behavior changes.
+8. Re-check after each fix.
+
+The reusable skill lives in `.gemini/skills/triage-findings/SKILL.md`.