cmd-speckit-taskstoissues

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/speckit.taskstoissues

Agent skill wrapper for the Claude command

/speckit.taskstoissues

When the original command text references

{{INPUT}}

$1

, or named arguments, map them from the user's current request.

Claude命令

/speckit.taskstoissues

的Agent技能封装。

当原始命令文本引用

{{INPUT}}

、

$1

或命名参数时，从用户当前请求中映射对应的值。

Command Instructions

命令说明

Create GitHub issues from the tasks in

tasks.md

, in dependency order. Skips already-completed tasks.

按照依赖顺序将

tasks.md

中的任务创建为GitHub Issues。跳过已完成的任务。

Safety rules (enforce strictly)

安全规则（严格执行）

Never create issues in a repository that does not match the current
```
git remote origin
```
.
Confirm
```
owner/repo
```
with the user before creating any issues.
Skip completed tasks (marked
```
[x]
```
) silently and note the count.
Escape special characters in issue titles and bodies.

绝不在与当前
```
git remote origin
```
不匹配的仓库中创建Issues。
在创建任何Issues之前，与用户确认
```
owner/repo
```
信息。
静默跳过已完成的任务（标记为
```
[x]
```
）并记录数量。
对Issue标题和正文中的特殊字符进行转义。

Steps

步骤

Locate tasks.md:
- If input names a feature or file path, use it.
- Otherwise check
```
.specify/specs/*/tasks.md
```
  ; if multiple, ask which.
- Fall back to
```
tasks.md
```
  in the project root.
Validate GitHub remote: Run
```
git config --get remote.origin.url
```
. Verify it returns a
```
github.com
```
URL. If not, stop: "This command requires a GitHub remote. The current remote is not a GitHub URL."
Identify the repository: Parse the remote URL to extract
```
owner/repo
```
. Display it and ask the user to confirm before creating any issues.
Parse tasks: Extract all tasks from
```
tasks.md
```
, preserving:
- Phase name and number
- Task ID (T001, T002, ...)
- Parallelizable flag (
```
[P]
```
  )
- User story reference (
```
[USn]
```
  )
- Task description and any file paths
Create issues for each incomplete task (not marked
```
[x]
```
), in phase and ID order:
- Title:
```
[Phase N] [T0XX] <task description>
```
- Body: Phase name, user story reference (if present), link to the feature spec file, task description.
- Labels: Create a
```
speckit
```
  label (color
```
#6366f1
```
  ) if absent. Add
```
phase-N
```
  label. Add
```
parallelizable
```
  label if
```
[P]
```
  .

Report a summary table:

Task ID | Issue # | Title                                   | Labels
T001    | #42     | [Phase 1] [T001] Create database models | speckit, phase-1, parallelizable
T003    | SKIPPED | Already completed                       | —

定位tasks.md:
- 如果输入指定了功能或文件路径，则使用该路径。
- 否则检查
```
.specify/specs/*/tasks.md
```
  ；如果存在多个，询问用户选择哪一个。
- 最后回退到项目根目录下的
```
tasks.md
```
  。
验证GitHub远程仓库: 运行
```
git config --get remote.origin.url
```
。验证返回的是
```
github.com
```
的URL。如果不是，则停止操作：“此命令需要GitHub远程仓库。当前远程仓库不是GitHub URL。”
识别仓库: 解析远程URL以提取
```
owner/repo
```
信息。在创建任何Issues之前，显示该信息并请求用户确认。
解析任务: 从
```
tasks.md
```
中提取所有任务，保留以下信息：
- 阶段名称和编号
- 任务ID（T001、T002等）
- 可并行标记（
```
[P]
```
  ）
- 用户故事引用（
```
[USn]
```
  ）
- 任务描述和所有文件路径
创建Issues: 按照阶段和ID顺序，为每个未完成的任务（未标记
```
[x]
```
）创建Issues：
- 标题:
```
[Phase N] [T0XX] <任务描述>
```
- 正文: 阶段名称、用户故事引用（如果存在）、功能规格文件链接、任务描述。
- 标签: 如果不存在
```
speckit
```
  标签（颜色
```
#6366f1
```
  ）则创建该标签。添加
```
phase-N
```
  标签。如果任务带有
```
[P]
```
  标记，添加
```
parallelizable
```
  标签。

生成报告: 输出汇总表格：

Task ID | Issue # | Title                                   | Labels
T001    | #42     | [Phase 1] [T001] Create database models | speckit, phase-1, parallelizable
T003    | SKIPPED | Already completed                       | —