Agent skill
tracker-github
GitHub Issues and Projects integration. Use for creating/updating issues, managing labels, adding to project boards, and tracking task status. Use when publishing artifacts, updating task status, or checking project state.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/tracker-github-arttttt-cmidcabot-4775544d
SKILL.md
GitHub Tracker
Configuration
- Repository: arttttt/CMIDCABot
- Project: CMI DCA Bot
Content Contract (MUST follow)
All content sent to GitHub MUST comply with these rules:
| Aspect | Requirement |
|---|---|
| Language | English only — translate Russian content before sending |
| Item title | From artifact # heading, no [Task]/[Brief] prefixes |
| Item body | Summary only — first paragraph, max 200 chars, truncate with "..." |
| Full content | As comment, not in body — use add_issue_comment |
| Comment header | ## Brief for BRIEF artifacts, ## Specification for TASK artifacts |
| Comment footer | ---\n_Source: \`_` |
Body Format
<summary in English, max 200 chars>
---
_Artifacts attached as comments below_
_Source: `<filepath>` (local, not yet in main)_
Comment Format
## Brief | Specification
<full artifact content, translated to English>
---
_Source: `<filepath>`_
Stage Flow
stage:brief → Backlog → /brief created
stage:spec → Todo → /spec created
stage:impl → In Progress → /implement started
stage:review → Review → /review created
(closed) → Done → PR merged
When to Use
- Creating GitHub Issues from artifacts
- Updating issue labels (stage transitions)
- Adding issues to Project board
- Moving issues between columns
- Querying project status
Quick Reference
Link Format
Tracker item link in artifact files:
<!-- GitHub Issue: #123 -->
Auto-close Syntax
To automatically close tracker item when PR is merged:
Closes #<number>
Status Mapping
| Abstract Status | GitHub Label | Project Column |
|---|---|---|
| backlog | stage:brief |
Backlog |
| todo | stage:spec |
Todo |
| implementation | stage:impl |
In Progress |
| review | stage:review |
Review |
| done | (Issue closed) | Done |
Create Issue
Use github:issue_write with method: "create":
owner: from Configurationrepo: from Configurationtitle: issue titlebody: issue bodylabels: array of label names
Get Issue
Use github:issue_read with method: "get":
owner: from Configurationrepo: from Configurationissue_number: issue number
Update Labels
Use github:issue_write with method: "update":
owner: from Configurationrepo: from Configurationissue_number: issue numberlabels: new array of label names
Update Status
To update tracker item status:
- Update label: remove old
stage:*, add newstage:* - Move to corresponding Project column
See Status Mapping table for label/column correspondence.
Add to Project
list_projectsto find project IDget_project_fieldsto get Status field IDadd_issue_to_projectto add issueupdate_project_item_fieldto set column
Move Column
Use move_item_to_column with project and column name.
Detailed References
- See
references/issues.mdfor issue operations - See
references/projects.mdfor project board operations
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?