Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[Feature]: Add a bundled `github` extension for taskstoissues

未关闭
  • 哪里不对？
#4,421 9 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@Yash-Chindam 已经在做这个了。

开始于 2026年9月8日。

评估

这个 Issue 还没有评估数据。

描述

feature-assess triage-must-have
Problem Statement

/speckit.taskstoissues creates GitHub issues from tasks.md, but GitHub issue tracking is provider-specific project-management functionality rather than part of the core Spec-Driven Development lifecycle.

Before the core command can be deprecated or removed, users need a fully functional extension-based replacement with an explicit installation and migration path.

Proposed Solution

Add a bundled, opt-in github-issues extension that provides the existing tasks-to-issues behavior under a namespaced command:

specify extension add github-issues
/speckit.github-issues.taskstoissues

Proposed manifest shape:

schema_version: "1.0"
extension:
  id: github-issues
  name: "GitHub Issues"
  version: "1.0.0"
  description: "Create GitHub issues from Spec Kit task lists"

provides:
  commands:
    - name: speckit.github-issues.taskstoissues
      file: commands/speckit.github-issues.taskstoissues.md
      description: "Convert tasks from tasks.md into dependency-ordered GitHub issues"

The extension command should preserve the current behavior:

  • Resolve the active feature and load tasks.md.
  • Confirm that the repository remote points to GitHub.
  • Detect existing issues by task ID across open and closed issues.
  • Create only missing issues in the repository identified by the remote.
  • Preserve the before_taskstoissues and after_taskstoissues hook contract.
  • Work across all supported integrations, including skills-based layouts.

The existing core /speckit.taskstoissues command must remain unchanged in this stage. The extension must not claim that legacy alias while the core command still exists.

Alternatives Considered
  • Deprecate the core command first: Rejected because users would receive a warning without having a working replacement.
  • Move the command immediately: Rejected because it would combine replacement, deprecation, and removal into one migration step.
  • Use a generic issues extension: A provider-specific extension makes GitHub tooling requirements explicit and leaves room for Jira, Linear, and other providers.
Component

Specify CLI (initialization, commands)

AI Agent (if applicable)

All agents

Use Cases
  1. Users can opt into GitHub issue creation without adding provider-specific behavior to the core SDD workflow.
  2. Extensions such as milestone grouping can declare a dependency on the namespaced GitHub Issues command.
  3. Alternative issue-tracker extensions can coexist without replacing a core GitHub-specific command.
Acceptance Criteria
  • A bundled github-issues extension can be installed with specify extension add github-issues.
  • The extension provides speckit.github-issues.taskstoissues for every supported integration.
  • The extension preserves current issue creation, remote validation, pagination, and deduplication behavior.
  • Existing before_taskstoissues and after_taskstoissues hooks execute as before.
  • The core speckit.taskstoissues command remains available and unchanged.
  • The extension does not register a legacy alias that conflicts with the core command.
  • Extension-specific tests cover installation, invocation artifacts, hooks, and uninstall behavior.
  • Documentation explains installation, usage, and the planned migration from the core command.
  • The change is included in a minor release.
Additional Context

This is stage 1 of a three-stage migration:

  1. Add the extension while retaining the core command.
  2. Deprecate the core command after the replacement is available.
  3. Remove the command from core in a later minor release.

Related discussion: #4370, especially https://github.com/github/spec-kit/issues/4370#issuecomment-5525946904.

The Jira preset/extension direction in #2223 should also be considered when documenting provider-specific issue-tracker integrations.

主要语言
Python
星标
141k
派生
12.6k
平均合并
23 小时 53 分钟
30 天内合并 PR
188

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

github/spec-kit 的其他 Issue

查看 github/spec-kit 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。