
Phoenix Github
- 12 installs
- 10.9k repo stars
- Updated August 4, 2026
- arize-ai/phoenix
phoenix-github is a Claude Code skill that manages GitHub issues, labels, and the roadmap project board for the Arize-ai/phoenix repository via the gh CLI.
About
phoenix-github is a reference for managing GitHub issues, labels, and project boards on the Arize-ai/phoenix repository using the gh CLI. Developers use it to file roadmap epics, triage bugs, apply the correct component and priority labels, and add issues to the Phoenix Roadmap project board. It includes the label taxonomy, roadmap issue templates, and GraphQL recipes for setting project fields.
- Manages GitHub issues, labels, and project boards for Arize-ai/phoenix
- Documents the c/ component label taxonomy and roadmap issue format
- Provides gh CLI and GraphQL recipes for the Phoenix Roadmap project board
Phoenix Github by the numbers
- 12 all-time installs (skills.sh)
- Ranked #415 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
phoenix-github capabilities & compatibility
- Capabilities
- issue triage · label management · project board management · roadmap planning
- Works with
- github
- Use cases
- project management
- Runs
- Runs locally
- Pricing
- Free
What phoenix-github says it does
Manage GitHub issues, labels, and project boards for the Arize-ai/phoenix repository.
Every issue should have at least one component label.
The canonical roadmap board for open-source Phoenix.
npx skills add https://github.com/arize-ai/phoenix --skill phoenix-githubAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 12 |
|---|---|
| repo stars | ★ 10.9k |
| Last updated | August 4, 2026 |
| Repository | arize-ai/phoenix ↗ |
What it does
File and triage GitHub issues, apply Phoenix labels, and manage the Phoenix Roadmap project board via the gh CLI.
Who is it for?
Maintainers filing roadmap epics, triaging issues, and managing the Phoenix project board
Skip if: Repos other than Arize-ai/phoenix, since the labels, project IDs, and field IDs are Phoenix-specific
When should I use this skill?
You are filing roadmap issues, triaging bugs, applying labels, or managing the Phoenix roadmap project board
What you get
Correctly labeled Phoenix issues and roadmap epics added to the project board with proper status and dates
- labeled GitHub issues
- roadmap epics
- project-board entries with status and dates
By the numbers
- 18 component (c/) labels
- 4 priority labels
- Phoenix Roadmap is Project #45
Files
Phoenix GitHub
Reference for managing issues, labels, and project boards on the Arize-ai/phoenix repository using the gh CLI.
Repository
Arize-ai/phoenixQuick Reference
| Task | See |
|---|---|
| File a roadmap epic | Roadmap Issues |
| Apply the right labels | Label Taxonomy |
| Add an issue to the roadmap project | Project Board |
| Set project dates or status | Project Board |
| Create a bug or feature request | Standard Issues |
---
Label Taxonomy
Component Labels (c/)
Every issue should have at least one component label.
| Label | Area |
|---|---|
c/ui | Frontend / React UI |
c/server | FastAPI backend / server logic |
c/traces | Tracing, spans, OpenTelemetry ingestion |
c/evals | Evaluations framework |
c/datasets | Datasets CRUD and management |
c/experiments | Experiment runs and comparisons |
c/annotations | Human annotations and queues |
c/prompts | Prompt management and prompt SDK |
c/playground | LLM playground and provider support |
c/agents | In-browser or terminal AI agents for Phoenix |
c/client | Python/TypeScript SDK and REST client |
c/rbac | Role-based access control |
c/auth | Authentication |
c/infra | Infrastructure, jobs, storage connectors |
c/mcp | MCP (Model Context Protocol) integration |
c/filters | Filter UI and filter logic |
c/metrics | Metrics and aggregations |
c/dx | Developer experience |
Priority Labels
| Label | Use |
|---|---|
priority: highest | Roadmap epics and critical P0 bugs |
priority: high | Important but not blocking |
priority: medium | Normal queue work |
priority: low | Nice-to-have |
Type / Status Labels
| Label | Use |
|---|---|
roadmap | High-level roadmap epic |
bug | Something isn't working |
enhancement | New feature or improvement |
documentation | Docs-only change |
triage | Needs triage by the team |
blocked | Blocked on external dependency |
backlog | Acknowledged but not scheduled |
needs information | Awaiting info from the reporter |
design | Needs design work before engineering |
onboarding | Related to new-user onboarding flows |
phoenix-cloud | Arize-hosted Phoenix (cloud) specific |
---
Roadmap Issues
Roadmap issues are high-level epics representing product initiatives.
Title Format
🗺️ [category] TitleCategories: ui/ux, agents, infrastructure, datasets/experiments, tracing, enterprise, server-evals, annotations, evals, prompts, sdk/connectors
Labels per Category
| Category | Labels |
|---|---|
ui/ux | roadmap, priority: highest, c/ui |
agents | roadmap, priority: highest, c/agents |
infrastructure | roadmap, priority: highest, c/infra |
datasets/experiments | roadmap, priority: highest, c/datasets, c/experiments |
tracing | roadmap, priority: highest, c/traces |
enterprise | roadmap, priority: highest, c/rbac, c/auth |
server-evals | roadmap, priority: highest, c/evals, c/server |
annotations | roadmap, priority: highest, c/annotations |
evals | roadmap, priority: highest, c/evals |
evals (with playground) | roadmap, priority: highest, c/evals, c/playground |
prompts | roadmap, priority: highest, c/prompts, c/playground |
sdk/connectors | roadmap, priority: highest, c/client |
Body Template
<one-line description of the initiative>
## Spike
- [ ]
## Front End
- [ ]
## Back End
- [ ]
## Open Questions
-Creating a Roadmap Issue
gh issue create \
--repo Arize-ai/phoenix \
--title "🗺️ [category] Title" \
--label "roadmap,priority: highest,c/ui" \
--body "$(cat <<'EOF'
Description of the initiative.
## Spike
- [ ]
## Front End
- [ ]
## Back End
- [ ]
## Open Questions
-
EOF
)"---
Project Board
Phoenix Roadmap (Project #45)
The canonical roadmap board for open-source Phoenix.
| Field | ID |
|---|---|
| Project ID | PVT_kwDOA5FfSM4AJaRo |
| Start Date | PVTF_lADOA5FfSM4AJaRozgInoCI |
| Target Date | PVTF_lADOA5FfSM4AJaRozgInn58 |
| Status | PVTSSF_lADOA5FfSM4AJaRozgFw9n0 |
Status option IDs:
| Status | Option ID |
|---|---|
| Todo | f75ad846 |
| In Progress | 47fc9ee4 |
| Done | 98236657 |
Add an Issue to the Project
# 1. Get the issue node ID
NODE_ID=$(gh api repos/Arize-ai/phoenix/issues/{number} --jq '.node_id')
# 2. Add to project, capture item ID
ITEM_ID=$(gh api graphql -f query='
mutation($project: ID!, $content: ID!) {
addProjectV2ItemById(input: {projectId: $project, contentId: $content}) {
item { id }
}
}' \
-f project="PVT_kwDOA5FfSM4AJaRo" \
-f content="$NODE_ID" \
--jq '.data.addProjectV2ItemById.item.id')Set Start / Target Date
gh api graphql -f query='
mutation($project: ID!, $item: ID!, $field: ID!, $value: Date!) {
updateProjectV2ItemFieldValue(input: {
projectId: $project, itemId: $item, fieldId: $field,
value: {date: $value}
}) { projectV2Item { id } }
}' \
-f project="PVT_kwDOA5FfSM4AJaRo" \
-f item="$ITEM_ID" \
-f field="PVTF_lADOA5FfSM4AJaRozgInoCI" \ # Start Date field
-f value="2026-04-01"Set Status
gh api graphql -f query='
mutation($project: ID!, $item: ID!, $field: ID!, $option: String!) {
updateProjectV2ItemFieldValue(input: {
projectId: $project, itemId: $item, fieldId: $field,
value: {singleSelectOptionId: $option}
}) { projectV2Item { id } }
}' \
-f project="PVT_kwDOA5FfSM4AJaRo" \
-f item="$ITEM_ID" \
-f field="PVTSSF_lADOA5FfSM4AJaRozgFw9n0" \
-f option="47fc9ee4" # In ProgressRemove an Issue from a Project
Requires the project item ID (not the issue number). Paginate if the project has many items:
gh api graphql -f query='
mutation($project: ID!, $item: ID!) {
deleteProjectV2Item(input: {projectId: $project, itemId: $item}) {
deletedItemId
}
}' \
-f project="PVT_kwDOA5FfSM4AJaRo" \
-f item="$ITEM_ID"Note:gh issue createdoes not support--json. Capture the issue URL from stdout and extract the number withgrep -oE '[0-9]+$'.
---
Standard Issues
Bug Report
gh issue create \
--repo Arize-ai/phoenix \
--title "Short description of the bug" \
--label "bug,triage,c/traces" \
--body "..."Feature Request
gh issue create \
--repo Arize-ai/phoenix \
--title "Short description of the feature" \
--label "enhancement,c/ui" \
--body "..."---
Existing Roadmap Issues (Q2 2026)
Issues #11618–#11666 on the Phoenix roadmap project (Start: 2026-02-20, Target: 2026-08-31):
| # | Category | Title |
|---|---|---|
| #11618 | ui/ux | Onboarding Tracing |
| #11619 | ui/ux | Onboarding for Evals / Datasets |
| #11620 | ui/ux | Home page |
| #11621 | ui/ux | Recents / Favorites |
| #11622 | ui/ux | AI Components |
| #11623 | ui/ux | Agent Sidebar |
| #11624 | ui/ux | File Drag-Drop |
| #11625 | ui/ux | Command K |
| #11626 | agents | Agent API |
| #11627 | agents | Routing |
| #11628 | agents | Tools |
| #11629 | infrastructure | Jobs |
| #11630 | infrastructure | Blob Store Connector |
| #11631 | infrastructure | Web Hooks |
| #11632 | datasets/experiments | External ID / Patch Declarative Datasets |
| #11633 | datasets/experiments | Schemas |
| #11634 | datasets/experiments | Files / Images |
| #11635 | datasets/experiments | Dataset as a Spreadsheet UX |
| #11636 | datasets/experiments | Annotations / Corrections on Experiments |
| #11637 | datasets/experiments | Experiment Charts |
| #11638 | datasets/experiments | Multi-User Support |
| #11639 | tracing | Attribute Filters |
| #11640 | tracing | Attribute Columns |
| #11641 | tracing | AI Search |
| #11642 | tracing | Online Evals |
| #11643 | tracing | Triggers |
| #11644 | tracing | Custom Trace Views |
| #11645 | tracing | Resource Tags |
| #11646 | enterprise | Custom RBAC |
| #11647 | enterprise | Custom Roles |
| #11648 | server-evals | Code Evaluators |
| #11649 | server-evals | Code Evaluator Packages |
| #11650 | server-evals | Project Evaluators |
| #11651 | annotations | Annotation Queues |
| #11652 | annotations | Optimization Direction UX |
| #11653 | annotations | Numeric Thresholding |
| #11654 | evals | Trajectory Evals |
| #11655 | evals | Multimodal Evals |
| #11656 | evals | Pairwise Evals |
| #11657 | evals | Agent as a Judge |
| #11658 | evals | Evals UX |
| #11659 | prompts | Model Configs |
| #11660 | prompts | Model Profiles |
| #11661 | prompts | Vendor Tools / Web Search |
| #11662 | prompts | Multiple Playgrounds |
| #11663 | prompts | Chat with Your Prompt |
| #11664 | prompts | Edit / Append to Dataset on Playground |
| #11665 | sdk/connectors | Session APIs |
| #11666 | sdk/connectors | Vitest / Pytest Integration |
Related skills
FAQ
What labels does every issue need?
Every issue should have at least one component label from the c/ taxonomy, such as c/ui or c/server.
Which project board is the roadmap?
The Phoenix Roadmap, Project #45, is the canonical roadmap board for open-source Phoenix.