make-tracking-issue

Creates or revises GitHub tracking issues with structured plans and acceptance gates.

33.3k|2.8k|Updated Oct 26, 2020
One-click install
npx skills add https://github.com/remix-run/remix --skill make-tracking-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-tracking-issue
Source: https://github.com/remix-run/remix/tree/main/.agents/skills/make-tracking-issue
Command: npx skills add https://github.com/remix-run/remix --skill make-tracking-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing a good implementation tracking issue is hard: issues often end up too vague to act on or so prescriptive they lock in implementation details prematurely. This Skill produces focused GitHub tracking issues for Remix changes that clearly state the target outcome, implementor context, a concise checkbox plan, compatibility concerns, and required acceptance gates.

Core Features & Use Cases

  • Structured Issue Drafting: Generates issues with a specific title, summary, context and requirements, a flat checkbox implementation plan, and plain-bullet required gates.
  • GitHub CLI Integration: Uses gh to confirm the target repository, search for duplicate issues, inspect templates and labels, create or edit the issue, and verify the final result.
  • Scope Discipline: Preserves decisions already made by the user, avoids reopening settled questions, and keeps prescriptive implementation details out of the plan.
  • Use Case: After deciding to move test-command parsing into @remix-run/cli, ask the Skill to open a tracking issue; it inspects the repository, drafts the outcome-focused plan, creates the issue with gh, and reads it back to confirm the title, body, and URL.

Quick Start

Use the make-tracking-issue skill to create a GitHub tracking issue for refactoring @remix-run/test with a concise plan and acceptance gates.

Frequently Asked Questions about make-tracking-issue

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

FAQPage Schema
How do I create a GitHub tracking issue for a code change?

Ask the Skill to create a tracking issue describing the change. It inspects the relevant code and package metadata, drafts a structured issue with a summary, context, checkbox plan, and gates, then creates it with the gh CLI and verifies the result.

What should a good implementation tracking issue include?

A good tracking issue includes a specific title naming the outcome, a summary of the problem and target state, non-obvious context for the implementor, a flat checkbox plan of work outcomes, and plain-bullet acceptance gates covering tests, builds, and packaging checks.

Does the Skill create the issue on GitHub automatically?

It only creates or edits the issue when you explicitly ask, since that is an external write. Otherwise it returns a draft. When it does write, it uses the gh CLI and reads the issue back to confirm the title, body, state, and URL.

How detailed should the implementation plan in a tracking issue be?

The plan should be a single flat checklist of outcomes, one concise sentence each, covering implementation, tests, docs, and packaging. It should avoid nested checklists, exact type shapes, file layouts, or command-by-command instructions unless already decided.

When should I not use a tracking issue for a change?

Avoid a tracking issue when the change is trivial and needs no coordination, or when it would require creating a general abstraction beyond the focused scope. The Skill also keeps historical changelog entries and unrelated cleanup out of the issue unless requested.