‹ 首页

issue-tracking

@dragoscirjan · 收录于 1 周前 · 上游提交 1 个月前

Manage tasks, epics, and bugs based on ISSUE_TRACKING environment variable. Use `env-get` to determine storage (fs or github) and tools.

场景任务跟踪缺陷管理项目协作

适合你，如果需要在不同存储间无缝管理项目任务。

/ 下载安装
https://github.com/dragoscirjan/opencode-config/tree/main/skills/issue-tracking ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add dragoscirjan/opencode-config/issue-tracking
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- dragoscirjan/opencode-config/issue-tracking
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify dragoscirjan/opencode-config/issue-tracking
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
0GitHub stars
~502最小装载
~502含声明引用
~1.1K文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 f561928 · 表述以原文为准
它做什么

安装后，Claude 会根据环境变量自动选择本地文件或 GitHub 来管理任务、史诗和缺陷。它会用 Gherkin 格式描述功能，并用表情符号前缀区分层级。

什么时候触发

当用户要求创建、查看或更新任务、史诗或缺陷时触发。Claude 会先读取 ISSUE_TRACKING 环境变量以确定存储方式。

装好后可以这样说
Claude 会调用 issue-list 工具并过滤类型。
Claude 会更新对应 issue 的状态。
技能原文 SKILL.md作者撰写 · MIT · f561928

Issue Tracking

  • Run env-get tool for the ISSUE_TRACKING variable to determine the issue tracking environment and available tools:
  • e.g., ISSUE_TRACKING=fs,issue-create,issue-list,issue-read means issues are stored locally in the file system, and you must use those tools to manage them.
  • e.g., ISSUE_TRACKING=github,gh,cvs_github means issues are stored on GitHub, and you should use the gh cli or cvs_github MCP tools.
Templates
  • Issues: Follow the instructions in skills/issue-tracking/issue.md to format your issue body.
  • Note: The YAML frontmatter (id, type, parent, etc.) is automatically added by the issue-create tool (when using fs). Do NOT add it yourself when creating an issue. You may update it later if necessary.
  • Comments: Format your updates and comments using skills/issue-tracking/comment.md.
Content & Format

When describing features, stories, or bugs, use the Gherkin format as much as possible for clarity:

As a [persona]
I want to [action]
So that [benefit/value]

# OR

Given [initial context/state]
And [more context]
When [action occurs]
And [more actions]
Then [expected outcome]
And [more outcomes]
Hierarchy & Emoticons

If not created for the file system (ISSUE_TRACKING=fs,...), the issue title MUST contain as prefix the exact emoticon (e.g., 🚀 Q3 Goals). Do NOT manage or use labels.

  • 🚀 Initiative (initiative): Top-level business goal.
  • 🏔️ Epic (epic): Large project phase.
  • 📖 Story (story): User-facing feature.
  • 🛠️ Task (task): Atomic implementation step.
  • 🐛 Bug (bug): Defect in a story.
  • 🐛 Bug (bug): Defect in an epic.
Issue Rules
  • Links over Text: Link to local .specs/ files in comments instead of pasting large content.
  • Hierarchy Links: Use markdown (#42) to link parent/child and dependent issues.
  • Report Failures: Always post execution failures as CVS comments so humans can see them.
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…