AugmentClaude

GitHub Issue Analyzer

Analyze GitHub issues for validity, priority, and recommended actions.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/analyze-issue-qusong0627/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Claude activates this skill based on the context of your request.

What this skill does

Analyze Issue

分析 GitHub Issue,判断其真实性、优先级、仓库责任边界与建议动作。

Repository: https://github.com/ZhuLinsen/daily_stock_analysis/issues

Usage

/analyze-issue <issue_number>

Instructions

分析时使用简洁中文,优先遵循仓库根目录 AGENTS.md

Step 1: 拉取 Issue 信息

gh issue view <issue_number> --repo ZhuLinsen/daily_stock_analysis
gh issue view <issue_number> --repo ZhuLinsen/daily_stock_analysis --comments

如为 bug,优先核对 issue 模板中是否提供了以下信息:

  • 是否已同步到最新版本
  • commit hash / 版本基线
  • 运行环境与复现步骤
  • 日志或报错信息

Step 2: 回答 4 个核心问题

  1. 版本是否明确
  2. 问题是否真实且可验证
  3. 是否属于仓库责任边界
  4. 是否值得立即处理

Step 3: 结合仓库现状做证据检查

  • 阅读相关代码、配置、测试、脚本、工作流与文档
  • 如果问题涉及 API、数据源 fallback、报告生成、通知发送、认证、桌面端、发布流程,明确写出影响面
  • 判断是实际 bug、环境配置问题、使用方式问题、还是外部依赖问题
  • 如怀疑已被修复,检查当前代码而不是只看 issue 描述

Step 4: 形成结论

至少给出以下字段:

  • 版本基线:最新 / 非最新 / 未提供
  • 是否合理:是/否 + 理由
  • 是否是 issue:是/否 + 理由
  • 是否好解决:是/否 + 难点
  • 结论成立 / 部分成立 / 不成立
  • 分类bug / feature / docs / question / external
  • 优先级P0 / P1 / P2 / P3
  • 难度easy / medium / hard
  • 建议动作立即修复 / 排期修复 / 文档澄清 / 关闭

Step 5: 生成分析文档

保存到 .claude/reviews/issues/issue-<number>.md

Output Document Format

# Issue #<number> Analysis

**Date**: YYYY-MM-DD
**Status**: Pending Review

## Summary

- 版本基线:
- 是否合理:
- 是否是 issue:
- 是否好解决:
- 结论:
- 分类:
- 优先级:
- 难度:
- 建议动作:

## Evidence

- 关键 issue 信息:
- 关键代码/脚本/工作流证据:

## Impact Scope

- 受影响模块:
- 受影响运行路径(本地 / Docker / GitHub Actions / API / Web / Desktop):

## Root Cause / Main Reasoning

<根因或主要判断依据>

## Proposed Handling

<建议修复、澄清或关闭方式>

若建议后续创建 PR,给出的 PR title 建议符合 `AGENTS.md`:使用 `<类型>: <修改内容>`,不添加 `[codex]`、`codex`、`autocode`、`copilot` 或其他工具/agent 来源前缀;该约定仅用于协作一致性提醒,不应单独作为 review process blocker。

## Risks And Rollback

- 风险点:
- 若修复,回滚方式:

## Draft Reply

<建议回复内容>

Allowed Auto-Actions (No Confirmation Needed)

  • 拉取 issue 详情与评论
  • 阅读相关代码、配置、脚本、工作流和文档
  • 生成分析文档

Actions Requiring Confirmation

执行以下动作前,先询问用户:

  1. 添加或修改标签
  2. 在 issue 下评论
  3. 关闭 issue
  4. 开始修复 issue

Related skills