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

[Bug]: /speckit-taskstoissues dedup matches bare task IDs across features — valid tasks are silently skipped

未关闭
#4,271 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
github
领域
cli, tooling

调研方向

打开 .claude/skills/speckit-taskstoissues/SKILL.md,检查 list_issues 流程中的去重步骤。跟踪当前 feature 目录和 task ID 的比较方式,然后在两个 feature 目录中验证 T001 的行为。当不同 feature 中的有效 task 被保留,并且在创建前立即重复执行 feature 加 task 检查时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

Version

spec-kit v1.0.1 (.claude/skills/speckit-taskstoissues/SKILL.md, dedup step around the list_issues flow)

Description

Task IDs like T001 are local to one feature's tasks.md and restart from T001 in every feature. The dedup step, however, matches repository issues by task ID without scoping to the current feature: if feature 001-auth already produced an issue titled with T001, then running /speckit-taskstoissues for feature 002-billing sees "T001 exists" and skips creating the issue for billing's T001 — a silent gap in the tracker, in exactly the multi-feature repos this command targets.

This is the inverse of #2968 (which was about creating duplicates): the fix direction there makes the matching aggressive enough to now suppress valid tasks.

Expected behavior

  • Include a stable feature identifier (the NNN-name spec dir) in each created issue's title or a label, and require both the feature identity and the task ID to match before skipping.
  • Re-check for existing feature+task issues immediately before creation so two concurrent invocations don't race the fetch-then-create sequence.
主要语言
Python
星标
138k
派生
12.4k
平均合并
3 天 4 小时
30 天内合并 PR
154

贡献指南

打开贡献指南

从这里开始

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

github/spec-kit 的其他 Issue

查看 github/spec-kit 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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