From af7cc4d9da3ceb0a107952d9729708c99a7d9ee6 Mon Sep 17 00:00:00 2001 From: AI Review Bot Date: Fri, 15 May 2026 05:10:10 +0000 Subject: [PATCH] chore: update ai-review findings [skip ci] --- .amazonq/rules/triage-findings.md | 2 +- .claude/skills/triage-findings/SKILL.md | 3 ++- .codex/skills/triage-findings/SKILL.md | 3 ++- .gemini/skills/triage-findings/SKILL.md | 3 ++- .github/copilot-instructions.md | 2 +- .github/skills/triage-findings/SKILL.md | 2 +- CLAUDE.md | 2 +- GEMINI.md | 2 +- 8 files changed, 11 insertions(+), 8 deletions(-) diff --git a/.amazonq/rules/triage-findings.md b/.amazonq/rules/triage-findings.md index f6468cd..4b65ce1 100644 --- a/.amazonq/rules/triage-findings.md +++ b/.amazonq/rules/triage-findings.md @@ -7,7 +7,7 @@ When the task is to triage review findings, follow this workflow: 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`. +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. diff --git a/.claude/skills/triage-findings/SKILL.md b/.claude/skills/triage-findings/SKILL.md index ac823cf..c4ab450 100644 --- a/.claude/skills/triage-findings/SKILL.md +++ b/.claude/skills/triage-findings/SKILL.md @@ -18,7 +18,7 @@ description: Triage findings, fix real issues, and exclude false positives. - info 3. Renumber from 1. 4. Fix real issues. -5. Put false positives into `.gitea/ai-review/exclusions.json`. +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 @@ -26,3 +26,4 @@ description: Triage findings, fix real issues, and exclude false positives. - 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 index 423d595..21476cb 100644 --- a/.codex/skills/triage-findings/SKILL.md +++ b/.codex/skills/triage-findings/SKILL.md @@ -21,7 +21,7 @@ It is also used when some findings are false positives and should be moved into 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. +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 @@ -41,4 +41,5 @@ After the list is merged and ordered, resolve the remaining findings one by one. - 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/.gemini/skills/triage-findings/SKILL.md b/.gemini/skills/triage-findings/SKILL.md index ac823cf..c4ab450 100644 --- a/.gemini/skills/triage-findings/SKILL.md +++ b/.gemini/skills/triage-findings/SKILL.md @@ -18,7 +18,7 @@ description: Triage findings, fix real issues, and exclude false positives. - info 3. Renumber from 1. 4. Fix real issues. -5. Put false positives into `.gitea/ai-review/exclusions.json`. +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 @@ -26,3 +26,4 @@ description: Triage findings, fix real issues, and exclude false positives. - 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/.github/copilot-instructions.md b/.github/copilot-instructions.md index 3b5f291..f1a77ef 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -7,7 +7,7 @@ Use the triage-finding workflow for review issue lists: 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`. +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. diff --git a/.github/skills/triage-findings/SKILL.md b/.github/skills/triage-findings/SKILL.md index e4cfde8..8ca4117 100644 --- a/.github/skills/triage-findings/SKILL.md +++ b/.github/skills/triage-findings/SKILL.md @@ -7,7 +7,7 @@ Use the triage-finding workflow for review issue lists: 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`. +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. diff --git a/CLAUDE.md b/CLAUDE.md index 92710d5..fa2403d 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -7,7 +7,7 @@ When the task is to triage review findings, follow this workflow: 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`. +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. diff --git a/GEMINI.md b/GEMINI.md index e4cfde8..8ca4117 100644 --- a/GEMINI.md +++ b/GEMINI.md @@ -7,7 +7,7 @@ Use the triage-finding workflow for review issue lists: 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`. +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.