Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
arize-ai avatar

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)
At a glance

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
From the docs

What phoenix-github says it does

Manage GitHub issues, labels, and project boards for the Arize-ai/phoenix repository.
SKILL.md
Every issue should have at least one component label.
SKILL.md
The canonical roadmap board for open-source Phoenix.
SKILL.md
npx skills add https://github.com/arize-ai/phoenix --skill phoenix-github

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs12
repo stars10.9k
Last updatedAugust 4, 2026
Repositoryarize-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

SKILL.mdMarkdownGitHub ↗

Phoenix GitHub

Reference for managing issues, labels, and project boards on the Arize-ai/phoenix repository using the gh CLI.

Repository

Arize-ai/phoenix

Quick Reference

TaskSee
File a roadmap epicRoadmap Issues
Apply the right labelsLabel Taxonomy
Add an issue to the roadmap projectProject Board
Set project dates or statusProject Board
Create a bug or feature requestStandard Issues

---

Label Taxonomy

Component Labels (c/)

Every issue should have at least one component label.

LabelArea
c/uiFrontend / React UI
c/serverFastAPI backend / server logic
c/tracesTracing, spans, OpenTelemetry ingestion
c/evalsEvaluations framework
c/datasetsDatasets CRUD and management
c/experimentsExperiment runs and comparisons
c/annotationsHuman annotations and queues
c/promptsPrompt management and prompt SDK
c/playgroundLLM playground and provider support
c/agentsIn-browser or terminal AI agents for Phoenix
c/clientPython/TypeScript SDK and REST client
c/rbacRole-based access control
c/authAuthentication
c/infraInfrastructure, jobs, storage connectors
c/mcpMCP (Model Context Protocol) integration
c/filtersFilter UI and filter logic
c/metricsMetrics and aggregations
c/dxDeveloper experience

Priority Labels

LabelUse
priority: highestRoadmap epics and critical P0 bugs
priority: highImportant but not blocking
priority: mediumNormal queue work
priority: lowNice-to-have

Type / Status Labels

LabelUse
roadmapHigh-level roadmap epic
bugSomething isn't working
enhancementNew feature or improvement
documentationDocs-only change
triageNeeds triage by the team
blockedBlocked on external dependency
backlogAcknowledged but not scheduled
needs informationAwaiting info from the reporter
designNeeds design work before engineering
onboardingRelated to new-user onboarding flows
phoenix-cloudArize-hosted Phoenix (cloud) specific

---

Roadmap Issues

Roadmap issues are high-level epics representing product initiatives.

Title Format

🗺️ [category] Title

Categories: ui/ux, agents, infrastructure, datasets/experiments, tracing, enterprise, server-evals, annotations, evals, prompts, sdk/connectors

Labels per Category

CategoryLabels
ui/uxroadmap, priority: highest, c/ui
agentsroadmap, priority: highest, c/agents
infrastructureroadmap, priority: highest, c/infra
datasets/experimentsroadmap, priority: highest, c/datasets, c/experiments
tracingroadmap, priority: highest, c/traces
enterpriseroadmap, priority: highest, c/rbac, c/auth
server-evalsroadmap, priority: highest, c/evals, c/server
annotationsroadmap, priority: highest, c/annotations
evalsroadmap, priority: highest, c/evals
evals (with playground)roadmap, priority: highest, c/evals, c/playground
promptsroadmap, priority: highest, c/prompts, c/playground
sdk/connectorsroadmap, 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.

FieldID
Project IDPVT_kwDOA5FfSM4AJaRo
Start DatePVTF_lADOA5FfSM4AJaRozgInoCI
Target DatePVTF_lADOA5FfSM4AJaRozgInn58
StatusPVTSSF_lADOA5FfSM4AJaRozgFw9n0

Status option IDs:

StatusOption ID
Todof75ad846
In Progress47fc9ee4
Done98236657

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 Progress

Remove 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 create does not support --json. Capture the issue URL from stdout and extract the number with grep -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):

#CategoryTitle
#11618ui/uxOnboarding Tracing
#11619ui/uxOnboarding for Evals / Datasets
#11620ui/uxHome page
#11621ui/uxRecents / Favorites
#11622ui/uxAI Components
#11623ui/uxAgent Sidebar
#11624ui/uxFile Drag-Drop
#11625ui/uxCommand K
#11626agentsAgent API
#11627agentsRouting
#11628agentsTools
#11629infrastructureJobs
#11630infrastructureBlob Store Connector
#11631infrastructureWeb Hooks
#11632datasets/experimentsExternal ID / Patch Declarative Datasets
#11633datasets/experimentsSchemas
#11634datasets/experimentsFiles / Images
#11635datasets/experimentsDataset as a Spreadsheet UX
#11636datasets/experimentsAnnotations / Corrections on Experiments
#11637datasets/experimentsExperiment Charts
#11638datasets/experimentsMulti-User Support
#11639tracingAttribute Filters
#11640tracingAttribute Columns
#11641tracingAI Search
#11642tracingOnline Evals
#11643tracingTriggers
#11644tracingCustom Trace Views
#11645tracingResource Tags
#11646enterpriseCustom RBAC
#11647enterpriseCustom Roles
#11648server-evalsCode Evaluators
#11649server-evalsCode Evaluator Packages
#11650server-evalsProject Evaluators
#11651annotationsAnnotation Queues
#11652annotationsOptimization Direction UX
#11653annotationsNumeric Thresholding
#11654evalsTrajectory Evals
#11655evalsMultimodal Evals
#11656evalsPairwise Evals
#11657evalsAgent as a Judge
#11658evalsEvals UX
#11659promptsModel Configs
#11660promptsModel Profiles
#11661promptsVendor Tools / Web Search
#11662promptsMultiple Playgrounds
#11663promptsChat with Your Prompt
#11664promptsEdit / Append to Dataset on Playground
#11665sdk/connectorsSession APIs
#11666sdk/connectorsVitest / 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.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.