Files
devops-skills/skills/gitea-issue-devops-agent/references/triage-standard.md

141 lines
4.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Triage Standard
## Quality Score (0-100)
- `+20` Expected vs actual is explicit.
- `+20` Reproduction steps are explicit.
- `+15` Environment is explicit (browser/device/version).
- `+15` Attachment exists (image/video/log).
- `+10` Title is specific enough to infer scope.
- `+20` Body has enough detail for engineering action.
`pass` = score `>= 70`.
## Status Decision
- `closed_but_unresolved`: issue is closed but has clear reporter feedback indicating “still not fixed”.
- `closed_open_reopen_candidate`: issue is closed, but a newer open issue has high title/body similarity and should be manually reviewed for mis-close or regression.
- `ready_for_fix`: open issue, quality pass, reproducible.
- `needs-info`: open issue, quality below threshold.
- `duplicate`: semantically same as another issue.
- `enhancement-epic`: feature scope too large for a single fix cycle; split into sub-issues first.
## Mandatory Review Gates
- `image-first`: when issue body/comments contain screenshots, review the image evidence before coding.
- `image-retrieval-proof`: include `attachment_urls_detected` and `attachments_downloaded` from audit summary to prove image intake worked.
- `real-ai-only`: for AI conversation/generation issues, verify against real provider APIs with valid keys. Do not close based on mock-only behavior.
- `closure-evidence`: close only with commit, test result, deploy proof, and verification path.
## Needs-Info Comment Template
Use this comment when score is below threshold:
```text
[issue-quality-feedback-v1]
当前工单暂不满足开发准入标准,已进入待补充队列。请补充以下信息后我们将立即纳入修复流程:
1) 复现步骤(至少 3 步)
2) 期望结果 vs 实际结果
3) 环境信息(浏览器/系统/时间)
4) 截图或录屏(建议标注异常区域)
```
## Guided Start Template
Use this at session start before any implementation:
```text
[devops-startup-check-v1]
开始处理前请提供:
1) 仓库地址(完整 URL 或 base_url + owner/repo
2) API Key具备 issue 读写权限)
3) 执行模式(三选一):
- automatic自动修复+提测循环,最终合并仍需工程师确认
- semi-automatic修复后先人工 review再提测循环
- manual全流程人工确认
可选:指定 reviewer、提测命令、部署环境、健康检查地址。
可选(推荐):主环境 URL、共享 QA URL、预览槽位池如 preview-a/preview-b和预览 URL 模板。
```
## Review Request Template (Semi-Automatic)
```text
[issue-review-request-v1]
已完成本轮修复,等待指定 reviewer 确认后进入提测:
- issue: #<number>
- branch: <branch>
- commit: <sha>
- change summary: <summary>
- risk: <risk notes>
- test plan: <plan>
请回复“review-approved”或给出修改意见。
```
## Test Submission Template
```text
[issue-test-submit-v1]
已按分支提测:
- issue: #<number>
- branch: <branch>
- commit: <sha>
- pipeline/test run: <url>
- environment: <env/version>
- preview slot: <slot>
- preview url: <url>
- deploy scope: <skip|client_only|server_only|full_stack|infra_only>
- server strategy: <reused-shared|dedicated-branch-server>
- verify steps: <steps>
如失败或结果不符合预期,将继续同分支迭代修复。
```
## Preview Slot Allocation Template
```text
[issue-preview-slot-v1]
已分配提测环境(按 issue+branch 绑定):
- issue: #<number>
- branch: <branch>
- slot: <preview-a|preview-b|...>
- preview url: <url>
- ttl: <hours>
说明:同一分支会复用该 slot关闭/合并后自动释放。
```
## Preview Slot Release Template
```text
[issue-preview-release-v1]
已释放提测环境:
- issue: #<number>
- branch: <branch>
- slot: <slot>
- reason: <merged|closed|ttl-expired|manual-release>
```
## Merge Approval Template
```text
[merge-approval-check-v1]
准备执行最终合并,请工程师确认:
- issue: #<number>
- branch: <branch>
- target: <target branch>
- review status: <approved/pending>
- test status: <passed/failed>
- release evidence: <links>
请明确回复“merge-approved”后再执行合并。
```
## Closure Comment Template
```text
[issue-verified-close-v1]
已修复并发布。
- commit: <sha>
- tests: <summary>
- deploy: <pipeline/run url>
- verify: <how verified>
如仍可复现,请附最新截图和复现步骤,我们将立即 reopen。
```