Create draft pull requests with Storybook title, label, and template conventions.
npx skills add https://github.com/anukkrit149/anukkrit-skills --skill pr-anukkrit149
Please help me install this Agent Skill. Skill: pr Source: https://github.com/anukkrit149/anukkrit-skills/tree/main/cloud/skills/pr Command: npx skills add https://github.com/anukkrit149/anukkrit-skills --skill pr-anukkrit149
It removes the friction of writing consistent pull requests by enforcing Storybook conventions for title, labels, and body formatting.
[Area]: [Description] titles with a standardized Area format for easier scanning.Category and CI labels so PRs route cleanly through review and sandbox workflows..github/PULL_REQUEST_TEMPLATE.md exactly, preserving all HTML comments while filling the relevant sections.Use the pr skill to open a draft pull request with your changes by following the Storybook title, label, and template requirements.
High-intent search queries and answers about installing and using this skill.
To create a draft pull request with Storybook conventions, you must enforce a standardized `[Area]: [Description]` title format, apply the correct `Category` and `CI` labels for sandbox routing, and fill the `.github/PULL_REQUEST_TEMPLATE.md` body exactly, preserving all HTML comments, before invoking `gh pr create --draft`.
The required title format for Storybook-style pull requests is `[Area]: [Description]`. This standardized Area format ensures the PR titles are easily scannable and properly route through the repository's review and sandbox CI workflows.
To preserve HTML comments when filling out a PR template body, you must use the repository's `.github/PULL_REQUEST_TEMPLATE.md` contents exactly. This means retaining all original HTML comments while filling the relevant sections with your specific code change or documentation update information.
Yes, you need specific labels for CI routing on your draft PRs. You must apply the required `Category` and `CI` labels computed by the workflow so that your pull requests route cleanly through the appropriate review and sandbox workflows.
Yes, you can use this workflow for documentation updates and dependency maintenance. The pull request creation process applies Storybook conventions to code changes, documentation updates, and dependency or maintenance work, ensuring all draft PRs follow sandbox routing rules.
Your GitHub draft PR may fail sandbox routing checks if the title format is non-standard, the required `Category` and `CI` labels are missing, or the PR template body does not exactly match the `.github/PULL_REQUEST_TEMPLATE.md` file contents including HTML comments.
tamago0224Create a GitHub pull request from a specification file using a template.
cnoe-ioAggregate open pull requests with reviewers, CI results, and age across repositories.
mpauloskyEnforce a dev-first two-branch Git workflow with branch naming and PR rules.
DexForceCreate template-compliant GitHub pull requests for EmbodiChain.