Shen Shi

Safety Rules

参见 _shared/core/safety-rules.md — 所有安全规则从共享层加载。

审视 (GitHub Triage)

GitHub 只读审查技能。分析开放的 Issues 和 PRs，生成有证据支持的报告。

Read-only GitHub analysis skill. Analyzes open issues and PRs with evidence-backed reports.

Quick Commands

核心原则/Core Principles

只读不写/Read-Only Policy

【绝对禁止/NEVER】
- gh issue comment - 不评论
- gh issue close - 不关闭
- gh pr merge - 不合并
- gh api -X POST/PUT/PATCH/DELETE - 不写入

【允许/ALLOWED】
- gh issue view / gh pr view - 读取数据
- gh api (GET only) - 读取 API
- git log/show/blame - 读取 git 历史
- Write - 仅写入报告文件到临时目录

证据规则/Evidence Rule

【证据要求】
每个事实陈述必须有 GitHub permalink 作为证明。
Every factual claim requires a GitHub permalink as proof.

Permalink 格式/Format:
https://github.com/{owner}/{repo}/blob/{commit_sha}/{path}#L{start}-L{end}

示例/Example:
❌ 错误/Wrong: "代码有 bug"
✓ 正确/Correct: "代码有 bug [证据](https://github.com/owner/repo/blob/abc123/src/file.py#L45-L50)"

工作流程/Workflow

Phase 1: 数据收集/Data Collection

## 数据收集/Data Collection

**仓库/Repo**: {owner}/{repo}
**时间/Time**: {timestamp}

### 开放 Issues/Open Issues
| # | 标题/Title | 标签/Labels | 创建时间/Created | 优先级/Priority |
|---|-----------|------------|----------------|---------------|
| 1 | {title} | {labels} | {date} | P0/P1/P2 |

### 开放 PRs/Open PRs
| # | 标题/Title | 状态/Status | CI 状态/CI | 创建时间/Created |
|---|-----------|------------|----------|----------------|
| 1 | {title} | {status} | {ci} | {date} |

Phase 2: Spawn Background Tasks

1 ISSUE/PR = 1 BACKGROUND TASK. NO EXCEPTIONS.

Classification

Per-Item Report Template

Each task writes to {REPORT_DIR}/{issue|pr}-{number}.md:

# Issue #{number}: {title}
**Type:** {QUESTION|BUG|FEATURE|OTHER} | **Author:** {author} | **Created:** {createdAt}

## Summary
[1-2 sentence summary with permalink evidence]

## Findings
- [Finding with permalink](https://github.com/{REPO}/blob/{SHA}/{path}#L{N})

## Recommended Action
[Specific, actionable next step]

## Evidence Trail
[All permalinks used in this report]

Phase 3: 报告汇总/Summary Report

## 审视报告/Triage Report

**仓库/Repo**: {owner}/{repo}
**日期/Date**: {date}
**分析范围/Scope**: {issues_count} Issues, {prs_count} PRs

### P0 - 紧急/Urgent
| # | 类型/Type | 问题/Issue | 证据/Evidence | 建议/Action |
|---|---------|-----------|--------------|------------|
| 123 | Bug | {描述} | [link] | {action} |

### PR 状态/PR Status
| # | 标题/Title | CI | 审查/Review | 状态/Status |
|---|-----------|---|----------|----------|
| 45 | {title} | ✅ | ⏳ | 待审查/Pending |

### 建议行动/Recommended Actions
1. 优先处理 P0 Issue #123
2. PR #45 需要额外审查
3. ...

输出目录/Output Directory

/tmp/{YYYYMMDD-HHmmss}/
├── issue-{N}.md    # Issue 分析报告
├── pr-{N}.md       # PR 分析报告
└── summary.md      # 汇总报告

使用示例/Examples

示例 1：审视仓库

用户/User: /审视 cycleuser/Skills

→ 收集开放 Issues 和 PRs/Collect open items
→ 并行分析每个项目/Parallel analysis
→ 生成报告到 /tmp/{datetime}/Generate reports
→ 输出汇总/Output summary

Example 2: Analyze Specific PR

用户/User: /analyze https://github.com/owner/repo/pull/123

→ 读取 PR 详情/Read PR details
→ 检查 CI 状态/Check CI status
→ 审查代码变更/Review code changes
→ 生成分析报告/Generate analysis report

Rules

• rules/evidence.md - 证据规则/Evidence Rules
• rules/classification.md - 问题分类/Classification
• rules/report-format.md - 报告格式/Report Format
• rules/anti-aigc.md - 分析报告反AIGC检测规则
• ../_shared/core/anti-aigc.md - 通用反AIGC检测规则（共享层）
• ../_shared/core/design-principles.md - 共享设计原则

配置选项/Configuration

Anti-Patterns / 反模式

Zero-Action Policy (强化版)

【FORBIDDEN - 绝对禁止】
gh issue comment / gh issue close / gh issue edit / gh issue reopen
gh pr comment / gh pr merge / gh pr review / gh pr edit / gh pr close
gh api -X POST / gh api -X PUT / gh api -X PATCH / gh api -X DELETE
git push / git checkout / git fetch / git pull / git worktree
curl -X POST to GitHub API

【ALLOWED - 允许】
gh issue view / gh pr view / gh api (GET only)
git log / git show / git blame / git diff
Write - 仅写入报告文件到临时目录
Grep / Read / Glob - 搜索代码库

Troubleshooting / 排查

GitHub API rate limit / API限流

• Symptom / 症状: 403 errors when querying Issues/PRs
• Fix / 解决: Use --token <ghp_token> for authenticated requests (5000/hr vs 60/hr); cache results locally to reduce API calls

Large repository timeout / 大仓库超时

• Symptom / 症状: Analyzing repos with >1000 open issues times out
• Fix / 解决: Use /审视 issues <repo> --limit 100 to paginate; increase --timeout parameter; analyze by label filter

Report generation stalls / 报告生成卡住

• Symptom / 症状: Report writing hangs at evidence collection phase
• Fix / 解决: Check for broken links in issue bodies; use --skip-links to skip link validation; reduce --max-depth for comment threads

Mixed-language issues / 多语言议题

• Symptom / 症状: Classification accuracy drops on bilingual repositories
• Fix / 解决: Use /审视 <URL> --lang zh or --lang en to force language detection; review classification rules for language-specific patterns

Edge Cases / 边界情况

• Empty repository: If repo has zero open issues/PRs, output "No issues or PRs found" instead of failing
• Archived repository: Issues are read-only, mark all as "archived" and skip classification
• Cross-repository references: When Issue references another repo's PR, fetch the reference but annotate it as external
• Deleted comments: Placeholder text may contain "[deleted]" — skip these in sentiment analysis
• Bot-generated issues: Issues from bots (dependabot, stale bot) flagged as automated type
• Issue templates: Template text in issue body skipped for analysis, only user-filled content used

AIGC-Aware Output / AIGC检测意识

GitHub triage analysis must include permalink evidence for every claim, specific priority classification, and actionable recommendations. No generic "this seems like a bug" without code-level evidence. See rules/anti-aigc.md for anti-AIGC detection rules.

核心要求：

• 每个判断必须有GitHub permalink作为证据
• 不写"这个问题涉及多个方面"，写具体分类和优先级P0/P1/P2
• 建议必须可操作，包含具体修复方案或指派建议

Version History / 版本历史

See Also / 相关技能

• /把关 from ba-guan — 基于证据模式的发布前审查 / Pre-publish review with evidence patterns
• /安检 from an-jian — Issues 的安全分类审查 / Security classification of issues