PR Management — Phoenix Agentic Engine Interface

Repo Context

• •Owner: rivie13
• •Repo: Phoenix-Agentic-Engine-Interface
• •Default branch: main

Create a Pull Request

Step 1: Check for PR template

mcp_github_github_get_file_contents(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", path=".github/PULL_REQUEST_TEMPLATE.md")

Step 2: Create the PR

mcp_github_github_create_pull_request(
  owner="rivie13",
  repo="Phoenix-Agentic-Engine-Interface",
  title="<descriptive title>",
  body="<description>",
  head="<feature-branch>",
  base="main"
)

PR description should include:

• •What was changed and why
• •Backward compatibility assessment for any contract changes
• •Test results (npm test output)
• •If fixtures changed: confirmation that backend golden tests also pass

List Open PRs

mcp_github_github_list_pull_requests(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", state="open")

Request Copilot Review

mcp_github_github_request_copilot_review(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", pullNumber=<PR_NUMBER>)

Branch conventions

• •feature/<name> — new features
• •fix/<name> — bug fixes
• •contract/<name> — contract/schema changes