72.8k
GitHub Stars
1
Bundled Files
4 months ago
Catalog Refreshed
5 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill lobehub/lobehub --skill pr- SKILL.md2.2 KB
Overview
This skill creates a pull request for the current branch, following the repository's branching and PR conventions. It ensures the branch is pushed, checks for existing PRs, assembles a compliant title and body, links related issues, and opens the PR in your browser when ready.
How this skill works
The skill inspects your local git state and remote tracking to determine the current branch, unpushed commits, and change summary. It checks for an existing PR for that branch, searches for related GitHub issues, prepares a PR title using gitmoji conventions, fills the PR body using the repository template and links issues, and then creates the PR targeting the canary development branch.
When to use it
- You want to create a PR from the branch you are currently on.
- You need a PR that targets the canary development branch (never main).
- You want to automatically link and reference related GitHub or Linear issues.
- You want a PR body formatted to the repository's template and release conventions.
- You want the PR opened in the browser for final review.
Best practices
- Always run the skill from the branch that contains your changes; it reads the current branch automatically.
- Ensure commit history and change summary are correct before creating the PR to produce an accurate title and description.
- Use concise gitmoji + conventional commit style in the title (e.g., ✨ feat(scope): description) to control release triggers.
- Link only closely related issues rather than broad umbrella issues; use magic keywords like Fixes #123 to close them.
- Keep all PR content in English and fill the provided testing instructions and checkboxes in the body.
Example use cases
- You finished a feature on a feature/ branch and want to submit it against canary with a properly formatted PR.
- You pushed fixes and need the skill to detect an existing PR and avoid creating a duplicate.
- You want to attach a Linear or GitHub issue to the PR using magic keywords so it closes automatically.
- You need a quick change summary and commit-based title crafted from unpushed commits.
FAQ
The skill will detect an existing PR and inform you instead of creating a duplicate.
Which branch does the PR target?
All PRs are created against the canary development branch; do not create PRs directly to main.
Will the skill push my branch if it has no upstream?
Yes. It pushes the branch and sets the upstream when needed, then creates the PR.