setup-tracker

Configures per-repository issue tracker, triage labels, and domain documentation layout for engineering skills.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/Suge8/skills --skill setup-tracker-suge8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-tracker
Source: https://github.com/Suge8/skills/tree/main/workflow/setup-tracker
Command: npx skills add https://github.com/Suge8/skills --skill setup-tracker-suge8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering skills like triage, ticket creation, and implementation need to know where a repository tracks issues, which label strings it uses, and where domain docs live. This Skill performs that one-time per-repository setup so every other engineering skill reads consistent configuration instead of guessing. ## Core Features & Use Cases - Issue Tracker Setup: Detects the repository's remote and configures GitHub (gh CLI), GitLab (glab CLI), local markdown files under .scratch/, or a custom tracker workflow. - Label Vocabulary Mapping: Writes a mapping from canonical triage, type, and lifecycle roles (needs-triage, ready-for-agent, in-progress, etc.) to the label strings the tracker actually uses. - Domain Docs Layout: Configures single-context (CONTEXT.md plus docs/adr/) or multi-context (CONTEXT-MAP.md) layouts with consumer rules for engineering skills. - Use Case: After cloning a new project, run this Skill once; it explores the repo, confirms choices with you, then writes docs/agents/issue-tracker.md, triage-labels.md, and domain.md plus an Agent skills block in CLAUDE.md or AGENTS.md. ## Quick Start Ask the agent to run the setup-tracker skill to configure this repository's issue tracker, labels, and domain docs before using other engineering skills.

Frequently Asked Questions about setup-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure an issue tracker for agent engineering skills?▼

Run the setup-tracker skill once per repository. It inspects your git remote, proposes GitHub, GitLab, or local markdown tracking, confirms with you, and writes the choice to docs/agents/issue-tracker.md for other skills to read.

Does this setup support GitLab or only GitHub issues?▼

Both are supported out of the box. GitHub uses the gh CLI and GitLab uses the glab CLI, each with its own seed template covering issue creation, labeling, lifecycle transitions, and wayfinding operations.

Can I use a local markdown issue tracker instead of GitHub?▼

Yes. The local markdown option stores issues as files under .scratch/<feature>/ with Status lines and a Comments section, which suits personal projects or repositories without a remote.

How do I customize triage label names for my tracker?▼

During setup you are asked whether to keep the default label vocabulary. If you answer no, you provide override strings, and the skill writes the role-to-label mapping into docs/agents/triage-labels.md so skills use your existing labels.

When should I rerun the repository tracker setup?▼

Only when switching issue trackers or starting over from scratch. Routine changes like renaming labels or editing tracker conventions are made by directly editing the files under docs/agents/.