Bug Assessment:
【免费下载链接】spec-kit💫 Toolkit to help you get started with Spec-Driven Development项目地址: https://gitcode.com/GitHub_Trending/sp/spec-kit
- Slug: <BUG_SLUG>
- Created: <ISO 8601 date>
- Source: <URL or "pasted text">
- Verdict: valid | likely valid, needs reproduction | invalid
- Severity: critical | high | medium | low
Report (verbatim or summarized)
<引用/浓缩的报告内容;若抓取了 URL,包含标题与短摘录并链接 URL。>
Symptom
<一两句话描述观察到的行为与预期行为。>
Reproduction
<未知处标记为 [NEEDS CLARIFICATION: …]>
Suspected Code Paths
path/to/file.py:42—path/to/other.ts:func()—
Root Cause Hypothesis
<一段话,并注明置信度:high / medium / low>
Proposed Remediation
Preferred: <一到两段描述变更。>
Alternatives(可选):
- <alternative + trade-off>
Files likely to change:
path/to/file.pypath/to/test_file.py
Tests to add or update:
Risks & Considerations
Open Questions
- [NEEDS CLARIFICATION: …]
7. **汇报** — 必须输出:所用 slug 及其来源(用户提供 / 询问所得 / 自动生成),并**单独占一行**(如 `Slug: <BUG_SLUG>`),方便同一下游命令从上下文直接复用而无需再次询问;`assessment.md` 的路径 `.specify/bugs/<BUG_SLUG>/assessment.md`;verdict 与 severity;以及下一步建议 `__SPECKIT_COMMAND_BUG_FIX__ slug=<BUG_SLUG>`。 ## 6. 下游衔接:占位符如何变成真实命令 `assessment.md` 中出现的 `__SPECKIT_COMMAND_BUG_FIX__`、`__SPECKIT_COMMAND_BUG_TEST__` 是命令间解耦的关键。安装/注册阶段,Spec-Kit 会把这类占位符替换为当前 Agent 实际暴露的调用形式。源码中这一逻辑集中在 [resolve_command_refs](https://link.gitcode.com/i/20259975329e4c516d9ad6eb08ffb3de): ```python @staticmethod def resolve_command_refs(content: str, separator: str = ".", prefix: str = "/") -> str: """Replace ``__SPECKIT_COMMAND_<NAME>__`` placeholders with invocations.""" return re.sub( r"__SPECKIT_COMMAND_([A-Z][A-Z0-9_]*)__", lambda m: prefix + "speckit" + separator + m.group(1).lower().replace("_", separator), content, )【免费下载链接】spec-kit💫 Toolkit to help you get started with Spec-Driven Development项目地址: https://gitcode.com/GitHub_Trending/sp/spec-kit
创作声明:本文部分内容由AI辅助生成(AIGC),仅供参考