Back to Details

analyze-issue

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Please analyze GitHub issue #$ARGUMENTS and create a technical specification.
Follow these steps:
  1. Check if the issue is already loaded:
    • Look for the issue file in 
      ./specs/issues/
      folder
    • File naming pattern: 
      <number-padded-to-3-digits>-<kebab-case-title>.md
    • If not found, fetch the issue details from GitHub (see step 2)
  2. Fetch the issue details (if not already loaded):
    • Read 
      .claude/commands/load-issues.md
      to understand how to fetch issue details
    • Save the issue file following the load-issues.md format
  3. Understand the requirements thoroughly
  4. Review related code and project structure
  5. Create a technical specification with the format below
请分析GitHub Issue #$ARGUMENTS并创建一份技术规格说明书。
请遵循以下步骤：
  1. 检查Issue是否已加载：
    • 在
      ./specs/issues/
      文件夹中查找Issue文件
    • 文件命名规则：
      <number-padded-to-3-digits>-<kebab-case-title>.md
    • 如果未找到，从GitHub获取Issue详情（见步骤2）
  2. 获取Issue详情（如果尚未加载）：
    • 阅读
      .claude/commands/load-issues.md
      以了解如何获取Issue详情
    • 按照load-issues.md的格式保存Issue文件
  3. 彻底理解需求
  4. 审阅相关代码和项目结构
  5. 按照以下格式创建技术规格说明书

Technical Specification for Issue #$ARGUMENTS

Issue #$ARGUMENTS的技术规格说明书

Issue Summary

Issue摘要

  • Title: [Issue title from GitHub]
  • Description: [Brief description from issue]
  • Labels: [Labels from issue]
  • Priority: [High/Medium/Low based on issue content]
  • 标题：[来自GitHub的Issue标题]
  • 描述：[Issue的简要描述]
  • 标签：[来自Issue的标签]
  • 优先级：[根据Issue内容确定高/中/低]

Problem Statement

问题陈述

[1-2 paragraphs explaining the problem]
[1-2段解释问题]

Technical Approach

技术方案

[Detailed technical approach]
[详细的技术方案]

Implementation Plan

实施计划

  1. [Step 1]
  2. [Step 2]
  3. [Step 3]
  1. [步骤1]
  2. [步骤2]
  3. [步骤3]

Test Plan

测试计划

  1. Unit Tests:
    • [test scenario]
  2. Component Tests:
    • [test scenario]
  3. Integration Tests:
    • [test scenario]
  1. 单元测试：
    • [测试场景]
  2. 组件测试：
    • [测试场景]
  3. 集成测试：
    • [测试场景]

Files to Modify

需要修改的文件

  • [文件路径]：[修改内容]

Files to Create

需要创建的文件

  • [文件路径]：[用途]

Existing Utilities to Leverage

可利用的现有工具

  • [工具名称/路径]：[用途]

Success Criteria

成功标准

  • [criterion 1]
  • [criterion 2]
  • [标准1]
  • [标准2]

Out of Scope

超出范围的内容

  • [item 1]
  • [item 2]
Remember to follow our strict TDD principles, KISS approach, and 300-line file limit.
IMPORTANT: After completing your analysis, SAVE the full technical specification to: 
./specs/issues/<number-padded-to-3-digits>-<kebab-case-title>.specs.md
For example, for issue #7 with title "Make code review trigger on any *.SQL and .sh file changes", save to: 
./specs/issues/007-make-code-review-trigger-on-sql-sh-changes.specs.md
After saving, provide a brief summary to the user confirming:
  • Issue number and title analyzed
  • File path where the specification was saved
  • Key highlights from the specification (2-3 bullet points)
  • [项1]
  • [项2]
请记住遵循我们严格的TDD原则、KISS方法以及单文件不超过300行的限制。
重要提示：完成分析后，将完整的技术规格说明书保存至： 
./specs/issues/<number-padded-to-3-digits>-<kebab-case-title>.specs.md
例如，对于编号为7、标题为“Make code review trigger on any *.SQL and .sh file changes”的Issue，保存至： 
./specs/issues/007-make-code-review-trigger-on-sql-sh-changes.specs.md
保存完成后，向用户提供一份简要总结，确认：
  • 已分析的Issue编号和标题
  • 规格说明书的保存路径
  • 规格说明书中的关键要点（2-3个项目符号）