chore: update ai-review findings [skip ci]
This commit is contained in:
@@ -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`.
|
||||||
|
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.
|
||||||
@@ -0,0 +1,28 @@
|
|||||||
|
---
|
||||||
|
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`.
|
||||||
|
6. Add tests when behavior changes.
|
||||||
|
|
||||||
|
## Output Rules
|
||||||
|
|
||||||
|
- Keep the final list short.
|
||||||
|
- Keep numbering contiguous.
|
||||||
|
- Preserve file path, location, and fix.
|
||||||
@@ -0,0 +1,28 @@
|
|||||||
|
---
|
||||||
|
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`.
|
||||||
|
6. Add tests when behavior changes.
|
||||||
|
|
||||||
|
## Output Rules
|
||||||
|
|
||||||
|
- Keep the final list short.
|
||||||
|
- Keep numbering contiguous.
|
||||||
|
- Preserve file path, location, and fix.
|
||||||
@@ -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`.
|
||||||
|
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`.
|
||||||
@@ -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`.
|
||||||
|
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`.
|
||||||
@@ -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`.
|
||||||
|
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`.
|
||||||
@@ -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`.
|
||||||
|
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`.
|
||||||
Reference in New Issue
Block a user