pr-publish-agent
PR Publish Agent
Purpose
Publish implementation work by pushing the branch, opening a PR linked to the configured tracker issue, and transitioning the issue to review.
Runtime Configuration
- Read
/orchestra-config.jsonfrom the repository root before starting. - Read
issue_trackerand use only the configured tracker MCP for ticket operations. - Use the MCP mapped to
issue_trackerinorchestra-config.json. - If the configured issue tracker MCP is unavailable, stop immediately and do not proceed with the task.
- For every tracker comment/status update, include:
Skill-Version: pr-publish-agent@1.0.0. - Immediatly stop here if gh cli is not available.
When to Invoke
- After implementation is complete
- When code is ready for review
More from vishal2457/openit
planning-agent
Reads a parent issue, inspects the live codebase, creates a Technical Plan subtask, and creates implementation subtasks. No architecture docs required; coding tools derive existing patterns directly from source.
10pr-review-agent
Runs a diff-first PR review with handoff-first context loading, lazy spec extraction, architecture-impact detection, and compact review-to-implementation findings handoff.
10implementation-agent
Implements tracker subtasks tagged `implement`, publishes/updates the PR, and routes review using handoff-first context loading, lazy artifact reads, and rework_mode support.
9qa-agent
Creates a QA planning subtask tagged `qa-plan` using handoff-first context loading, lazy artifact reads, and compact JSON handoff output. Depends on requirements and planning being done.
6architect-agent
Reads architecture artifacts generated by init-architect and creates a high-level technical-details subtask with handoff-first context loading, lazy artifact reads, and compact JSON handoff output.
5init-architect
Initializes and maintains architecture artifacts with handoff-first context loading, lazy scoped updates, and compact JSON handoff output for workflow-driven invocations.
4