update-issue-tree

Synchronize GitHub issue phase labels and reassign orphan issues.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/Fandhe-AI/agent-cli-skills --skill update-issue-tree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-issue-tree
Source: https://github.com/Fandhe-AI/agent-cli-skills/tree/main/skills/update-issue-tree
Command: npx skills add https://github.com/Fandhe-AI/agent-cli-skills --skill update-issue-tree

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the management and synchronization of GitHub Issue Trees, ensuring consistent phase labeling and resolving orphan issues.

Core Features & Use Cases

  • Recursive Issue Tree Retrieval: Retrieves and organizes all issues in a GitHub repository's Issue Tree, including sub-issues.
  • Phase Synchronization: Synchronizes phase labels across issues, ensuring consistency within the Issue Tree.
  • Orphan Issue Resolution: Identifies and reassigns orphan issues to appropriate phase parents.
  • New Phase Parent Creation: Creates new phase parents as needed for new tasks that do not fit within existing phases.
  • Quick Start: Use the update-issue-tree skill with the root tracking issue number as an argument.

Quick Start

Execute the update-issue-tree command with the root tracking issue number.

update-issue-tree 42

Frequently Asked Questions about update-issue-tree

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

FAQPage Schema
How do I synchronize phase labels across a GitHub issue tree?

You can synchronize phase labels by running the update-issue-tree command with the root tracking issue number, which recursively retrieves all sub-issues and enforces phase label consistency across the entire tree.

What is the best way to resolve orphan issues in a GitHub repository?

Resolving orphan issues in a GitHub repository is handled by identifying unparented issues and automatically reassigning them to appropriate phase parents within the existing issue tree structure.

Do I need the gh CLI to automate GitHub issue tree management?

Yes, the gh CLI is required because this Skill depends on it for GitHub API access to retrieve issue trees, update phase labels, and reassign orphan issues automatically.

Can I create new phase parents for GitHub issues that do not fit existing phases?

Yes, you can create new phase parents for GitHub issues, as this Skill detects new tasks that do not fit within existing phases and automatically generates the necessary phase parents.

How does recursive issue tree retrieval work for GitHub sub-issues?

Recursive issue tree retrieval works by fetching and organizing all issues in a GitHub repository, traversing through nested sub-issues to build a complete hierarchical view before synchronizing phases.