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.

16 stars

Best use case

phoenix-github is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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.

Teams using phoenix-github should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/phoenix-github/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/cli-automation/phoenix-github/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/phoenix-github/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How phoenix-github Compares

Feature / Agentphoenix-githubStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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

| Task | See |
|---|---|
| File a roadmap epic | [Roadmap Issues](#roadmap-issues) |
| Apply the right labels | [Label Taxonomy](#label-taxonomy) |
| Add an issue to the roadmap project | [Project Board](#project-board) |
| Set project dates or status | [Project Board](#project-board) |
| Create a bug or feature request | [Standard Issues](#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] Title
```

**Categories:** `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

```markdown
<one-line description of the initiative>

## Spike

- [ ]

## Front End

- [ ]

## Back End

- [ ]

## Open Questions

-
```

### Creating a Roadmap Issue

```bash
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

```bash
# 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

```bash
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

```bash
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:

```bash
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

```bash
gh issue create \
  --repo Arize-ai/phoenix \
  --title "Short description of the bug" \
  --label "bug,triage,c/traces" \
  --body "..."
```

### Feature Request

```bash
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

python-github-actions

16
from diegosouzapw/awesome-omni-skill

Complete Python GitHub Actions system. PROACTIVELY activate for: (1) uv-based CI workflows (10-100x faster), (2) Matrix testing across Python versions, (3) Dependency caching with setup-uv, (4) Parallel test execution, (5) Reusable workflows, (6) Publishing to PyPI with trusted publishing, (7) Code coverage with codecov, (8) Security scanning. Provides: Workflow templates, caching config, matrix strategies, composite actions. Ensures fast, reliable CI/CD pipelines.

github

16
from diegosouzapw/awesome-omni-skill

Access GitHub repositories via the GitHub REST API. Use this skill when the user wants to interact with GitHub including reading files, creating/updating files, listing repos, managing branches, viewing commits, working with issues, or managing pull requests. All scripts use PEP 723 inline metadata for dependencies and run via `uv run`. Requires GITHUB_TOKEN environment variable (a Personal Access Token with appropriate scopes).

github-workflow-automation

16
from diegosouzapw/awesome-omni-skill

Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management

github-search

16
from diegosouzapw/awesome-omni-skill

Search GitHub for repos, code, and usage examples using gh CLI. Capabilities: repo discovery, code search, finding library usage patterns, issue/PR search. Actions: search, find, discover repos/code/examples. Keywords: gh, github, search repos, search code, find examples, how to use library, stars, language filter. Use when: finding repositories, searching code patterns, discovering how libraries are used, exploring open source.

github-release-management

16
from diegosouzapw/awesome-omni-skill

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management

github-ops

16
from diegosouzapw/awesome-omni-skill

Workflow for repository reconnaissance and operations using GitHub CLI (gh). Optimizes token usage by using structured API queries instead of blind file fetching.

github-multi-repo

16
from diegosouzapw/awesome-omni-skill

Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration

github-issues

16
from diegosouzapw/awesome-omni-skill

Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.

github-issue

16
from diegosouzapw/awesome-omni-skill

Work on a GitHub issue end-to-end: checkout main, create branch, research best practices, plan implementation, write tests first (TDD), implement, run code review, QA validation, then create PR. Use when given a GitHub issue URL or number to implement.

github-issue-creator

16
from diegosouzapw/awesome-omni-skill

Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wan...

github-expert

16
from diegosouzapw/awesome-omni-skill

Complete GitHub expertise covering GitHub Actions, CI/CD workflows, automation, repository management, and best practices. Use when setting up GitHub Actions, creating workflows, managing pull requests, configuring automation (Dependabot, CodeQL), or implementing GitHub best practices. Includes workflow generators, templates, and production-ready configurations.

github-copilot-cli-expert

16
from diegosouzapw/awesome-omni-skill

Expert knowledge of GitHub Copilot CLI - installation, configuration, usage, custom agents, MCP servers, and version management. Use when asking about copilot cli, copilot commands, installing copilot, updating copilot, copilot features.