此技能根据仓库配置中的变更跟踪规则创建或查找GitHub Issues工单。它解决了确定代码变更所属工单的问题。当需要创建或查找工单时使用,仅支持GitHub Issues。
安装
npx skillscat add dracocephalum/dc-agentics/change-tracking 通过 SkillsCat registry 安装。
此技能根据仓库配置中的变更跟踪规则创建或查找GitHub Issues工单。它解决了确定代码变更所属工单的问题。当需要创建或查找工单时使用,仅支持GitHub Issues。
Change tracking per this repository's rules. GitHub Issues is the only
supported tracker today; for anything else, say so and stop.
Find the rules
First .dc-agentics.yaml at the repository root: change-tracking.tracker
is github-issues or none - with none there is nothing to create and
this skill says so and stops; source-control.mode says whether creating a
ticket asks first. Then read the rule in the first location that exists,
then the tracker file it names. Never work from memory.
| Rule | Initialized repository | dc-agentics toolkit |
|---|---|---|
| change tracking - the ticket rule, the setting, the initialization exception, boards; names the tracker file | docs/rules/change-tracking/change-tracking.md |
repo/payload/docs/rules/change-tracking/change-tracking.md |
Actions from $ARGUMENTS
| Argument | Do | Where the procedure is |
|---|---|---|
new "<what and why>" |
create the ticket and report its number | change tracking, Before any work; tracker file, Tickets |
find <#n | words> |
show the ticket, or the tickets matching the words | tracker file, Tickets |
Always
A ticket is a sentence of intent, not a design document. Creating one is a
host action: it follows source-control.mode in the source-control rules,
For an agent. Nothing is invented that the user did not give - not the
ticket's intent, not which ticket the work belongs to.