find-unplanned-issues

Audit GitHub issues for missing masterplan ancestry and prune closed descendants.

57.9k|4.4k|Updated Jun 23, 2020
One-click install
npx skills add https://github.com/remotion-dev/remotion --skill find-unplanned-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-unplanned-issues
Source: https://github.com/remotion-dev/remotion/tree/main/.agents/skills/find-unplanned-issues
Command: npx skills add https://github.com/remotion-dev/remotion --skill find-unplanned-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Large repositories accumulate open issues that drift away from their strategic masterplan hierarchy, making it hard to track progress and identify orphaned work. This Skill surfaces those gaps and cleans up closed branches so the masterplan tree stays accurate.

Core Features & Use Cases

  • Masterplan Coverage Audit: Recursively walks the parent chain of every open issue to flag those lacking a masterplan ancestor, distinguishing between issues with no parent and those whose parent chain never reaches a masterplan.
  • Closed Issue Pruning: Recursively traverses the masterplan rooted at issue #9081, reparenting open children before removing closed issues so live work stays tracked.
  • Use Case: Run the audit weekly in CI to catch newly created issues that were never linked to a masterplan, then schedule a cleanup pass to detach closed sub-issues from the Remotion roadmap.

Quick Start

Run the find-unplanned-issues skill to audit the Remotion masterplan hierarchy and report any open issues missing a masterplan ancestor.

Frequently Asked Questions about find-unplanned-issues

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

FAQPage Schema
How do I find GitHub issues not linked to a masterplan?

Run the bundled script with `bun find-unplanned-issues.ts` from the repository root. It lists every open issue whose parent chain does not reach an issue titled with "masterplan", separating issues with no parent from those with non-masterplan ancestors.

How to prune closed issues from a GitHub masterplan tree?

Use `bun prune-closed-masterplan-issues.ts` to preview closed descendants of the root masterplan. Pass `--apply` to reparent open children to the grandparent and remove the closed issue from its parent.

Does the audit require an authenticated gh CLI?

Yes. The scripts invoke `gh issue list` and `gh issue view`, which require an authenticated GitHub CLI session that supports the `parent` JSON field. Without authentication, the commands fail with a non-zero exit code.

Can I audit a different GitHub repository with this skill?

Pass `--repo owner/repo` to the audit script to inspect another repository. The prune script accepts `--root` with a full GitHub issue URL to target a different masterplan hierarchy.

Why are some issues excluded from the audit report?

Masterplan issues themselves are omitted, and a repository-specific exemption list excludes long-running trackers like issue #8375 that intentionally stand outside the masterplan hierarchy.