External Issue Tracking
Track issues on third-party repos, monitor PRs, and coordinate open-source contributions.
External Issue Tracking
VantagePeers tracks issues and PRs on external GitHub repos. This enables coordinated open-source contributions — an orchestrator (Zeta) fixes bugs on third-party projects while Pi monitors PR status.
Workflow
Pi identifies issue on external repo
|
v
/track-external-issue {repo} {number}
|
v
Issue created in VantagePeers (with external fields)
|
v
Mission created from repo-fix-v1 template (10 tasks)
|
v
Zeta receives notification + starts working
|
v
Zeta submits PR → prStatus updated
|
v
PR Monitor cron polls hourly → notifies Pi on merge/closeExternal Issue Fields
| Field | Type | Description |
|---|---|---|
externalRepo | string | Third-party repo (e.g., get-convex/better-auth) |
externalIssueNumber | number | Issue number on the external repo |
externalIssueUrl | string | Full URL to the issue |
prUrl | string | URL of the submitted PR |
prStatus | draft | open | merged | closed | Current PR state |
forkRepo | string | Our fork (e.g., elpiarthera/better-auth) |
PR Monitor Cron
A cron runs every hour and checks all external issues with prStatus = open or draft. For each:
- Fetches PR state from GitHub API
- If merged → updates
prStatustomerged, notifies Pi - If closed without merge → updates to
closed, notifies Pi
No manual checking needed — Pi gets a message when any PR changes state.
Tools
External issue tracking uses the standard VantagePeers tools: create_task, update_task, and list_tasks with appropriate tags. There are no dedicated external-tracking MCP tools — the /track-external-issue skill below handles the full workflow.
Skill: /track-external-issue
Usage: /track-external-issue {owner/repo} {issue_number}
The skill automates the full workflow: fetches the issue from GitHub, creates it in VantagePeers, creates a mission from the repo-fix-v1 template, and notifies Zeta.