Enforce PR title and description formats with Jira linking via GitHub CLI.
npx skills add https://github.com/promptlylabs/skills --skill pr-writer-promptlylabs
Please help me install this Agent Skill. Skill: pr-writer Source: https://github.com/promptlylabs/skills/tree/main/plugins/promptly-skills/skills/pr-writer Command: npx skills add https://github.com/promptlylabs/skills --skill pr-writer-promptlylabs
Ensures pull requests are created and updated according to Promptly Health conventions, reducing review back-and-forth and misaligned metadata by enforcing standardized titles, descriptions, and Jira linking.
Generate a draft PR title and description that follow the project conventions and embed the Jira ticket reference.
High-intent search queries and answers about installing and using this skill.
Standardize pull request titles and descriptions by enforcing PR format conventions and applying structured templates, which reduces review back-and-forth and misaligned metadata. The Skill validates title and body structure against project conventions before a PR is drafted or updated.
Automatically link Jira tickets to a pull request by detecting the ticket reference directly from the branch name. The Skill extracts the Jira identifier during PR creation and embeds it into the PR metadata to maintain traceability across plan-driven changes.
Yes, you need GitHub CLI or API access to draft, update, and link Jira tickets for pull requests with enforced conventions. This access is required to apply structural checks, manage draft PR workflows, and prevent non-conforming PRs from being merged.
The best way to generate a draft PR description is using a ready-to-use template workflow that enforces project conventions. This standardizes the PR creation process by applying consistent title and body structures, ensuring reviews start with aligned metadata.
Yes, you can update PR metadata via the GitHub API when managing plan-driven branch changes. The Skill supports updating PR titles and descriptions to maintain compliance with conventions as the branch evolves, preventing non-conforming PRs from slipping through.
A pull request gets blocked for not following code review conventions because automated checks validate the PR title, body structure, and Jira linking. This enforcement prevents non-conforming PRs from bypassing the standardized review workflow required by the project.
flurdyCreate pull requests from feature branches using Jira ticket parsing.
wonderslifeCreate pull requests and run automated review checks for validated code changes.
tigredonorteUpdate PR descriptions and attach visual documentation for Jira-tied tasks.
zaziedlmGenerate PR-ready titles and descriptions from git diffs and commit history.
