resolve-tracker-issue

Convert one flagged GitHub tracker issue into a repository integration plan.

Updated May 27, 2026
One-click install
npx skills add https://github.com/frankdevlabs/digital-omnibus-2025-0360 --skill resolve-tracker-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-tracker-issue
Source: https://github.com/frankdevlabs/digital-omnibus-2025-0360/tree/main/.claude/skills/resolve-tracker-issue
Command: npx skills add https://github.com/frankdevlabs/digital-omnibus-2025-0360 --skill resolve-tracker-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve?

This Skill turns one flagged tracker issue into a clear, source-backed integration plan so the repository can absorb new developments without mixing unrelated issues together.

Core Features & Use Cases

  • Single-issue triage: Handles exactly one open tracker issue per run and produces one focused plan file.
  • Source-aware classification: Reads the GitHub issue body, extracts the source metadata, and joins it to the repository watchlist.
  • Playbook routing: Directs the issue to the right workflow for institutional updates, Council texts, Parliament texts, stakeholder items, or source-health problems.
  • Plan and PR workflow: Writes a triage plan under docs/triage and can optionally branch, commit, and open a draft pull request.
  • Use case: A tracker alert surfaces a new Council compromise text, and this Skill identifies the downstream files that need updating and lays out the exact steps.

Quick Start

Resolve issue number 18 and generate the triage plan for the flagged tracker source.

Frequently Asked Questions about resolve-tracker-issue

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

FAQPage Schema
How do I triage a flagged GitHub issue into a repository integration plan?

To triage a flagged GitHub tracker issue, you parse the issue body, join source metadata to the repository watchlist, select a playbook, and generate a focused docs/triage plan for repository integration.

What is legislative tracker issue triage for source health and institutional updates?

Legislative tracker issue triage classifies flagged GitHub issues by routing them to specific playbooks for institutional updates, Council texts, Parliament texts, stakeholder items, or source-health problems to produce actionable integration plans.

Can I automatically create a draft pull request from a tracker issue triage plan?

Yes, the triage workflow can optionally branch the repository, commit the generated plan file, and open a draft pull request after writing the triage plan under docs/triage for the resolved tracker issue.

Does this tracker issue triage process support batch processing multiple GitHub issues at once?

No, the triage process handles exactly one open GitHub tracker issue per run to ensure a focused repository integration plan without mixing unrelated issues together, requiring separate runs for each flagged issue.

Do I need pyyaml to run the tracker issue triage and plan generation workflow?

Yes, pyyaml is required as a dependency to parse the YAML watchlist and source metadata needed for playbook routing and generating the triage plan for flagged tracker issues.