Phoenix Github Manage GitHub issues, labels, and project boards for the Arize-ai/phoenix repository. Use when filing roadmap issues, triaging bugs, applying labels, managing the Phoenix roadmap project board, or querying issue/project state via the GitHub CLI.
Arize-ai 9,333 estrellas 20 feb 2026
Ocupación Categorías Flujos de Trabajo Git Contenido de la habilidad
Reference for managing issues, labels, and project boards on the Arize-ai/phoenix repository using the gh CLI.
Repository
Arize-ai/phoenix
Quick Reference
Instalación rápida
Phoenix Github npx skills add Arize-ai/phoenix
estrellas 9,333
Actualizado 20 feb 2026
Ocupación
Label Taxonomy
Component Labels (c/) Every issue should have at least one component label.
Label Area 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 Label Use priority: highestRoadmap epics and critical P0 bugs priority: highImportant but not blocking priority: mediumNormal queue work priority: lowNice-to-have
Type / Status Labels Label Use 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.
Categories: ui/ux, agents, infrastructure, datasets/experiments, tracing, enterprise, server-evals, annotations, evals, prompts, sdk/connectors
Labels per Category Category Labels ui/uxroadmap, priority: highest, c/uiagentsroadmap, priority: highest, c/agentsinfrastructureroadmap, priority: highest, c/infradatasets/experimentsroadmap, priority: highest, c/datasets, c/experimentstracingroadmap, priority: highest, c/tracesenterpriseroadmap, priority: highest, c/rbac, c/authserver-evalsroadmap, priority: highest, c/evals, c/serverannotationsroadmap, priority: highest, c/annotationsevalsroadmap, priority: highest, c/evalsevals (with playground)roadmap, priority: highest, c/evals, c/playgroundpromptsroadmap, priority: highest, c/prompts, c/playgroundsdk/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.
Field ID Project ID PVT_kwDOA5FfSM4AJaRoStart Date PVTF_lADOA5FfSM4AJaRozgInoCITarget Date PVTF_lADOA5FfSM4AJaRozgInn58Status PVTSSF_lADOA5FfSM4AJaRozgFw9n0
Status Option ID Todo f75ad846In Progress 47fc9ee4Done 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 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):
# 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
02
Quick Reference
#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
#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
Flujos de Trabajo Git
Repository Setup Initialize a worktree-based repo layout for parallel development. Creates a main worktree, a reviews worktree for PR reviews, and N numbered work branches. Handles .env creation, dependency installation, and branchlet config. TRIGGER when user asks to set up the repo from scratch, initialize worktrees, bootstrap their dev environment, "setup repo", "setup worktrees", "initialize dev environment", "set up branches", or when a freshly cloned repo has no sibling worktrees.
Significant-Gravitas 183.5k
Phoenix Github | Skills Pool