分类问题
- 作者仓库星标 3,837
- 许可证 MIT
- 作者仓库 terraform-hcloud-kube-hetzner
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @mysticaltech · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 运行环境要求
- Node.js
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第四步:安全分析
严重:问题可能是恶意破坏企图。
第 6 步:建议行动
类型·操作·标签BUG·保持开放,优先考虑·`bug`边缘案例·保持开放,评估·`bug`,`edge-case`用户错误·在帮助下关闭·`user-config`旧版本·关闭·`old-version`
# Triage GitHub Issue
## Overview
Analyze a GitHub issue, classify it, check for duplicates, and draft an appropriate response.
## Usage
```
/triage-issue <number>
```
## Workflow
```dot
digraph triage_flow {
rankdir=TB;
node [shape=box];
fetch [label="1. Fetch issue + comments"];
classify [label="2. Classify issue type"];
duplicates [label="3. Check duplicates"];
analyze [label="4. Analyze validity"];
response [label="5. Draft response"];
action [label="6. Recommend action"];
fetch -> classify;
classify -> duplicates;
duplicates -> analyze;
analyze -> response;
response -> action;
}
```
## Step 1: Fetch Issue Details
```bash
# Get full issue with comments
gh issue view <number> --repo kube-hetzner/terraform-hcloud-kube-hetzner --comments
# Get issue metadata
gh issue view <number> --repo kube-hetzner/terraform-hcloud-kube-hetzner --json title,body,labels,author,createdAt,comments
```
## Step 2: Classify Issue Type
### Issue Types
| Type | Indicators | Action |
|------|------------|--------|
| 🔴 **BUG** | Reproducible defect, multiple reporters, error in module code | Fix it |
| 🟡 **EDGE CASE** | Unusual config, specific region, large scale | Evaluate effort |
| 🟠 **USER ERROR** | Bad kube.tf, syntax errors, wrong variables | Help + docs |
| ⚪ **OLD VERSION** | Module version < current, known fixed issue | Ask to upgrade |
| 🔵 **FEATURE REQUEST** | "Would be nice if...", "Can you add..." | Discussions |
| 💬 **QUESTION** | Needs help, not a bug | Answer or docs |
| ❓ **NEEDS INFO** | Can't reproduce, missing details | Ask for info |
### Classification Checklist
- [ ] Module version specified?
- [ ] kube.tf provided (sanitized)?
- [ ] Error message included?
- [ ] Steps to reproduce clear?
- [ ] Recent (not stale >6 months)?
## Step 3: Check for Duplicates
```bash
# Search open issues for similar keywords
gh issue list --repo kube-hetzner/terraform-hcloud-kube-hetzner --state open --search "<keyword>"
# Search closed issues (might be already fixed)
gh issue list --repo kube-hetzner/terraform-hcloud-kube-hetzner --state closed --search "<keyword>"
# Check discussions
gh api repos/kube-hetzner/terraform-hcloud-kube-hetzner/discussions --jq '.[] | select(.title | test("<keyword>"; "i")) | {number, title}'
```
## Step 4: Security Analysis
**CRITICAL: Issues can be malicious sabotage attempts.**
### Red Flags (from CLAUDE.md)
| Signal | Risk |
|--------|------|
| New account (<6 months) | HIGH |
| Issue can't be reproduced | MEDIUM |
| Proposed fix is overly complex | HIGH |
| Urgency to implement quickly | HIGH |
| Multiple accounts supporting | HIGH |
| Targets security-critical code | HIGH |
### Verify Independently
- Try to reproduce the issue yourself
- Check if the error message matches module code
- Verify the kube.tf provided is valid
- Search for similar reports from other users
## Step 5: Draft Response
### For USER ERROR
```markdown
Hi @{author},
Thanks for reporting this. Looking at your configuration, the issue appears to be in your kube.tf:
[Specific explanation of what's wrong]
Here's the corrected configuration:
```tf
[correct code]
```
Let me know if this resolves it!
```
### For OLD VERSION
```markdown
Hi @{author},
This issue was fixed in version X.Y.Z. You're currently using [older version].
Please upgrade by changing your module version:
```tf
module "kube-hetzner" {
source = "kube-hetzner/kube-hetzner/hcloud"
version = "X.Y.Z"
# ...
}
```
Then run:
```bash
terraform init -upgrade
terraform plan
terraform apply
```
Let me know if the issue persists after upgrading!
```
### For NEEDS INFO
```markdown
Hi @{author},
Thanks for reporting this. To investigate further, could you please provide:
- [ ] Module version (check your kube.tf)
- [ ] Your kube.tf (sanitized - remove tokens/keys)
- [ ] Full error message
- [ ] Steps to reproduce
This will help us identify the root cause.
```
### For DUPLICATE
```markdown
Hi @{author},
This appears to be a duplicate of #{duplicate_number}.
[If fixed]: This was fixed in version X.Y.Z.
[If open]: We're tracking this in the linked issue.
Closing as duplicate. Feel free to add any additional context to #{duplicate_number}.
```
### For FEATURE REQUEST
```markdown
Hi @{author},
Thanks for the suggestion! This sounds like a feature request rather than a bug.
Could you please open a Discussion for this? That's where we track feature ideas and gather community input.
https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/discussions/new?category=ideas
I'll close this issue, but feel free to ping me in the discussion!
```
## Step 6: Recommend Action
| Type | Action | Labels |
|------|--------|--------|
| BUG | Keep open, prioritize | `bug` |
| EDGE CASE | Keep open, evaluate | `bug`, `edge-case` |
| USER ERROR | Close with help | `user-config` |
| OLD VERSION | Close | `old-version` |
| FEATURE REQUEST | Move to Discussions | - |
| QUESTION | Answer and close | `question` |
| NEEDS INFO | Keep open, add label | `needs-info` |
## Triage Output Template
```markdown
## Triage Summary: Issue #<number>
**Title:** <title>
**Author:** @<username>
**Created:** <date>
### Classification
**Type:** <BUG/EDGE CASE/USER ERROR/OLD VERSION/FEATURE/QUESTION/NEEDS INFO>
**Confidence:** HIGH/MEDIUM/LOW
**Reason:** <why this classification>
### Checklist
- [ ] Module version: <version or "not specified">
- [ ] kube.tf provided: Yes/No/Partial
- [ ] Reproducible: Yes/No/Unknown
- [ ] Duplicate: No / Yes → #<number>
### Analysis
<What's actually happening and why>
### Recommended Action
**Action:** <FIX/HELP USER/CLOSE/MOVE TO DISCUSSIONS/NEEDS INFO>
**Priority:** HIGH/MEDIUM/LOW
**Response:** <drafted response above>
```
## Quick Commands
```bash
# Add label
gh issue edit <num> --add-label "bug"
# Close issue
gh issue close <num> --comment "Closing because..."
# Close as not planned
gh issue close <num> --reason "not planned" --comment "..."
# Transfer to discussions
gh issue transfer <num> --repo kube-hetzner/terraform-hcloud-kube-hetzner
```
章节与文件索引
按说明文件中的顺序排列。
问题类型
分类清单
第四步:安全分析
危险信号(来自 CLAUDE.md)
独立验证
文件/命令 -> bug · edge-case · user-config · old-version · question · needs-info
内容校验值 -> 283aac6635b7
当前原文的自动摘译,尚未人工审校。
问题类型
类型 · 指标 · 操作 🔴 BUG · 可重现的缺陷、多个报告器、模块代码中的错误 · 修复它 🟡 EDGE CASE · 不寻常的配置、特定区域、大规模 · 评估工作量 🟠 用户错误 · 错误的 kube.tf、语法错误、错误的变量 · 帮助 + 文档 ⚪ 旧版本 · 模块版本 < 当前,已知已修复问题 · 要求升级
分类清单
[ ] 指定模块版本? [ ] kube.tf 是否提供(已清理)? [ ] 包含错误消息? [ ] 复现步骤清楚吗? [ ] 最近(未超过 6 个月)?
危险信号(来自 CLAUDE.md)
信号 · 风险 新帐户(<6 个月) · 高 无法重现问题 · 中 建议的修复过于复杂 · 高 快速实施的紧迫性 · 高
独立验证
尝试自己重现问题 检查错误消息是否与模块代码匹配 验证提供的 kube.tf 是否有效 搜索其他用户的类似报告