Agent skill · software engineering · remotion-dev
find-unplanned-issues
Audit and clean the Remotion GitHub masterplan hierarchy. Use when finding open issues that lack a masterplan ancestor, identifying orphaned issues that need a parent, or recursively removing closed issues from the masterplan rooted at issue #9081.
Why this skill is useful
Adds executable scripts for auditing and cleaning GitHub issue hierarchies that are not available in public documentation.
What it needs
Requires bun, gh installed locally. About 1k tokens when loaded. Last updated 2026-08-06. 55,698 stars on the source repository.
What this skill does
Find unplanned issues Run the bundled read-only audit from the repository root: The script treats an issue as planned when its title contains masterplan or any issue in its parent chain has a title containing masterplan. Masterplan issues themselves are omitted from the report. Repository-specific exceptions are also omitted; currently, issue #8375 is exempt because the long-running CI flake tracker intentionally stands on its own. Results distinguish between: no parent: the open issue has no parent at all. no masterplan ancestor: the issue has a parent, but following the complete parent chain does not reach a masterplan. Use a different repository or machine-readable output when needed: Pass --check for automation. It exits with status 1 when unplanned issues are found and 0 when every non-exempt open issue belongs to a masterplan. The audit requires an authenticated gh CLI that supports the parent JSON field. It only reads issue data. To fix findings, use the issue-management skill and verify each relationship after editing it. Remove closed issues from the masterplan Preview all closed descendants of the root masterplan recursively: The default root is <https://github.com/remotion-dev/remotion/issues/9081>. Override it only when intentionally auditing a different hierarchy: The command is a dry run unless --apply is passed. During application, process closed issues deepest-first and verify every relationship after changing it. If a closed issue has open children, move those children to its parent before removing the closed issue so open work stays in the masterplan. Use --json for a machine-readable dry-run report. Never pass --apply merely to test the script; it changes live GitHub issue relationships.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills remotion-dev/find-unplanned-issues