How do I install the Tracker Github skill?

Run npx skillmds@latest add majiayu000/tracker-github in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tracker Github safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tracker Github?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tracker Github free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tracker Github?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tracker Github by majiayu000 — Agent Skill

Name: Tracker Github
Rating: 4.2 (5 reviews)
Author: majiayu000

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.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

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 Configuration
repo: from Configuration
title: issue title
body: issue body
labels: array of label names

Get Issue

Use github:issue_read with method: "get":

owner: from Configuration
repo: from Configuration
issue_number: issue number

Update Labels

Use github:issue_write with method: "update":

owner: from Configuration
repo: from Configuration
issue_number: issue number
labels: new array of label names

Update Status

To update tracker item status:

Update label: remove old stage:*, add new stage:*
Move to corresponding Project column

See Status Mapping table for label/column correspondence.

Add to Project

list_projects to find project ID
get_project_fields to get Status field ID
add_issue_to_project to add issue
update_project_item_field to set column

Move Column

Use move_item_to_column with project and column name.

Detailed References

See references/issues.md for issue operations
See references/projects.md for project board operations

---name: tracker-githubdescription: 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.--- # 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: \`<filepath>\`_` | ### Body Format ``` <summary in English, max 200 chars> --- _Artifacts attached as comments below_ _Source: `<filepath>` (local, not yet in main)_ ``` ### Comment Format ```markdown ## 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: ```markdown  ``` ### Auto-close Syntax To automatically close tracker item when PR is merged: ```markdown 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 Configuration - `repo`: from Configuration - `title`: issue title - `body`: issue body - `labels`: array of label names ### Get Issue Use `github:issue_read` with `method: "get"`: - `owner`: from Configuration - `repo`: from Configuration - `issue_number`: issue number ### Update Labels Use `github:issue_write` with `method: "update"`: - `owner`: from Configuration - `repo`: from Configuration - `issue_number`: issue number - `labels`: new array of label names ### Update Status To update tracker item status: 1. Update label: remove old `stage:*`, add new `stage:*` 2. Move to corresponding Project column See Status Mapping table for label/column correspondence. ### Add to Project 1. `list_projects` to find project ID 2. `get_project_fields` to get Status field ID 3. `add_issue_to_project` to add issue 4. `update_project_item_field` to set column ### Move Column Use `move_item_to_column` with project and column name. ## Detailed References - See `references/issues.md` for issue operations - See `references/projects.md` for project board operations

Frequently asked questions