skunexus-backend-pr

Drafts and publishes GitHub pull request descriptions grounded in ticket artifacts and the real diff.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/SkuNexus-Devs/skunexus-ai --skill skunexus-backend-pr-skunexus-devs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skunexus-backend-pr
Source: https://github.com/SkuNexus-Devs/skunexus-ai/tree/main/skills/skunexus-backend-pr
Command: npx skills add https://github.com/SkuNexus-Devs/skunexus-ai --skill skunexus-backend-pr-skunexus-devs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing a trustworthy PR description requires reconciling planning artifacts, Jira tickets, and the actual code diff — a tedious process where descriptions often drift from what the code really does or miss the rationale reviewers need. ## Core Features & Use Cases - Artifact-grounded drafting: Builds the PR title and body from .ai/<TICKET>/ artifacts (prd.md, decisions.md, investigation.md, backend-plan.md) with the real git diff as final authority on behavior. - PR history detection: Detects open or previously merged PRs for the branch/ticket via gh and proposes full, updated, or delta-only descriptions accordingly. - Review-gated publishing: Writes the draft to .ai/<TICKET>/pr.md for developer review and only pushes the branch and opens a draft PR on GitHub after explicit approval. - Use Case: After finishing implementation on branch PHG-418, ask for a PR draft; the skill reads the diff and artifacts, writes pr.md with a What & why / Changes body, and on your approval runs gh pr create --draft. ## Quick Start Ask the assistant to draft the PR for the current ticket branch, for example: draft the PR for PHG-418 against dev.

Frequently Asked Questions about skunexus-backend-pr

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

FAQPage Schema
How do I draft a GitHub PR description from a ticket branch?

Run the skill on the ticket branch; it diffs against the base branch, reads the .ai/<TICKET>/ artifacts, and writes a draft to .ai/<TICKET>/pr.md. After you approve the draft, it pushes the branch and creates a draft PR with gh pr create.

How do I update an existing PR description after review changes?

The skill detects the open PR via gh pr list, compares its current description against the current diff, and proposes what to re-describe. On approval it updates the PR with gh pr edit without changing its draft or ready state.

Does it require the gh CLI to create pull requests?

Yes, pushing the branch and creating or editing the PR on GitHub is done through the authenticated gh CLI. Drafting the pr.md file itself only needs git and the local artifacts.

What happens if the planning artifacts are missing?

The skill falls back through a chain: artifacts, then the Jira ticket, then git commit messages, then targeted questions to the developer. It never invents rationale that cannot be grounded in a source.

When should a PR description cover only the delta of new work?

When an earlier PR on the same ticket was already merged, the skill proposes a delta-only description covering just the new work with a one-line reference to the previous round. This avoids re-explaining already-merged changes.