capability-publish-pr

Publishes a completed story branch as a review-ready pull request with quality gate and board updates.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/learnn-com/engineering-kb --skill capability-publish-pr-learnn-com
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capability-publish-pr
Source: https://github.com/learnn-com/engineering-kb/tree/main/.skills/capability-publish-pr
Command: npx skills add https://github.com/learnn-com/engineering-kb --skill capability-publish-pr-learnn-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates the repetitive, error-prone sequence of taking a finished story branch to a review-ready pull request: running the quality gate, composing the PR from a template, propagating classification tags, updating the project board, and dispatching the code review — all without duplicating PRs or losing cross-links between the code host and the PM tool. ## Core Features & Use Cases - Gated PR creation/update: Runs a quality gate first and halts on failure; creates exactly one PR per story or updates the existing one in place, never merging. - Template-driven PR body: Fills the pr-template with summary, story context, changes, and testing, including conditional sections (services to release, screenshots) only when pertinent. - Cross-tool synchronization: Copies story tags to the PR, posts a back-link comment on the PM item when code host and PM tool differ, and moves the board state to Review. - Enforced review flow: Registers a pending pair-review check that blocks merge from the start and dispatches the review to a clean-context subagent. - Use Case: After finishing a feature branch, invoke the skill with a story ID or handoff checkpoint to get a ready-for-review PR, an updated board, and a dispatched review in one step. ## Quick Start Publish my current story branch as a pull request using the handoff checkpoint for story 212.

Frequently Asked Questions about capability-publish-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a story branch as a pull request automatically?▼

Invoke the skill with a story ID or handoff checkpoint path. It runs the quality gate, composes the PR from the pr-template, pushes the branch, creates or updates the PR, and marks it ready for review in one sequence.

What happens if a pull request already exists for my branch?▼

The skill updates the existing PR's body and tags in place rather than opening a second one. It enforces a strict one-PR-per-story rule and is idempotent across re-runs.

Does this skill merge the pull request after review?▼

No. It never merges and never renders a review verdict. It registers a pending pair-review check that blocks merging, dispatches the review to a clean-context subagent, and stops at a PR under review.

What happens when the quality gate fails before creating a PR?▼

The skill halts before any PR is created or updated and reports each failing gate with its first failing detail. No PR side effects occur on a red gate.

Can it work when the code host and project management tool are different?▼

Yes. The PR is created on the code host while board state is updated on the PM tool, and a back-link comment with the PR URL is posted on the PM item. When both are the same tool, the cross-link step is skipped entirely.

What if no subagent can be spawned to run the code review?▼

The pending pair-review check stays in place so the merge remains blocked, and the skill posts a PR comment with instructions to run the review in a fresh session. It never runs the review inline in the authoring session.