github-tracking

Enforce epic updates for every pipeline command output when issue tracking is enabled.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/djwmobley/pipeline --skill github-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-tracking
Source: https://github.com/djwmobley/pipeline/tree/main/skills/github-tracking
Command: npx skills add https://github.com/djwmobley/pipeline --skill github-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This rule enforces that every pipeline command that produces output must update the associated epic, ensuring traceable, auditable progress across the feature lifecycle.

Core Features & Use Cases

  • Mandatory epic updates for all output-producing commands
  • Automatic epic checklist management and linking of findings to child issues when they are created
  • Graceful degradation when issue tracking is disabled or unavailable

Quick Start

Enable issue tracking in your config and run a command that emits output to observe automatic epic updates.

Frequently Asked Questions about github-tracking

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

FAQPage Schema
How do I enforce issue tracking updates for every GitHub pipeline command?

Issue tracking updates are enforced by checking configuration flags, resolving the associated epic, and updating the checklist whenever a pipeline command produces output. This ensures traceable, auditable progress across the feature lifecycle.

How do I link findings to child issues when an epic is updated?

Findings are linked to child issues by creating them automatically when predefined thresholds are met during the pipeline execution. The system resolves the epic, updates the checklist, and posts epic comments to maintain auditability.

What happens to epic updates when issue tracking is disabled?

When issue tracking is disabled or unavailable, the pipeline degrades gracefully by skipping the mandatory epic updates and child issue creation. This allows commands to execute without interruption while tracking remains inactive.

Can I automate epic checklist management across brainstorm through ship phases?

Yes, epic checklist management and linking of findings to child issues are applied automatically across brainstorm through ship phases. This occurs whenever issue tracking is enabled and a command emits output.

Why does my pipeline command not update the associated epic automatically?

Automatic epic updates fail if issue tracking is disabled in the configuration or if the system cannot resolve the target epic. Verify that tracking flags are enabled and the epic is correctly linked before running output-producing commands.