phoenix-github

Manage GitHub issues, project boards, sprints, and roadmap epics via the gh CLI.

11.3k|1.1k|Updated Nov 9, 2022
One-click install
npx skills add https://github.com/Arize-ai/phoenix --skill phoenix-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phoenix-github
Source: https://github.com/Arize-ai/phoenix/tree/main/.agents/skills/phoenix-github
Command: npx skills add https://github.com/Arize-ai/phoenix --skill phoenix-github

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Keeping a large GitHub project board accurate is manual and error-prone: slipped sprint tickets go unnoticed, assignee workloads become unbalanced, and roadmap epics drift out of date. This Skill automates sprint close-out, board hygiene audits, ticket-load balancing, standup reporting, and roadmap health checks for the Arize-ai/phoenix repository.

Core Features & Use Cases

  • Sprint Operations: Snapshot the sprint board (#42), dry-run a rollover plan, then apply it to move slipped tickets to the next sprint with an automatic comment on each issue.
  • Board Hygiene & Load Health: Detect stranded tickets, Done-but-open issues, unassigned in-progress work, and teammates who are starving (under 3 tickets) or buried (over 15).
  • Standup & Roadmap Audits: Generate per-person did/doing standup reports and audit roadmap board #45 epics for planning specificity, staleness, overdue dates, and missing Status fields, applying a needs planning label where warranted.
  • Use Case: At the end of a sprint, run the snapshot and rollover scripts to review which tickets slipped, apply the rollover, then run the health report to rebalance assignments before the next sprint planning meeting.

Quick Start

Ask the assistant to close out the current sprint on the phoenix board and roll any unfinished tickets into the next sprint.

Frequently Asked Questions about phoenix-github

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

FAQPage Schema
How do I roll over unfinished sprint tickets on a GitHub project board?

Take a board snapshot with snapshot.sh, run rollover.py to review the dry-run plan, then run it with --apply to move open tickets to the next sprint and post a slip comment on each. Iteration IDs are resolved live since they rotate every sprint.

How do I check ticket load balance across a GitHub project team?

Run health.py with the load section against a board snapshot. It reports each roster member's current-sprint and total open ticket counts, flagging anyone under 3 tickets (starving) or over 15 (overloaded), plus work assigned outside the roster team.

Can GitHub project sprint iterations be created via the API?

No, new iterations cannot be created through the GitHub API. If no future sprint exists, you must add it to the Sprint field in the GitHub UI before running a rollover; the scripts fail with a clear message rather than guessing.

Why does a board snapshot go stale for write operations?

A snapshot is a read cache, not a source of truth: tickets closed or moved after it was taken still read as open in the file. rollover.py refuses to apply from snapshots older than 2 hours unless you pass --stale-ok.

How are roadmap epics flagged as needing planning?

roadmap.py parses the epic body's checkbox list and flags an epic when it has no checklist or when fewer than 50% of remaining unchecked items reference real issues. With --apply it adds or removes the needs planning label to match reality.