Automated summary
This skill opens a pull request for the current branch with a conventional title, structured description, and pre-flight checks (lint, typecheck, tests).
Strengths
- Automates the full flow: pre-flight checks, branch commit/diff analysis, title and body drafting, then creation via gh
- Title follows conventional commit format derived from the overall branch intent rather than individual commits
- Pushes the branch upstream automatically when it isn't yet tracked
Limitations
- Assumes a Bun-based stack (lint, typecheck, test) and a GitHub repo with an authenticated gh CLI
- Always compares against main, which may be wrong if your base branch differs
- Does not auto-fix lint or test failures — it only surfaces errors and asks the user how to proceed
Reach for it when your branch is ready and you want to quickly open a well-formatted GitHub PR without hand-writing the title and description.
Skip it if your repo doesn't use GitHub/gh CLI or a Bun toolchain, or if your base branch isn't main.
Security analysis
CautionThe skill is transparent and uses Bash for legitimate git/PR workflow automation. It does not exfiltrate secrets or run destructive commands, but it does execute package scripts and perform remote-modifying operations (`git push`, `gh pr create`), so it warrants caution rather than being classified safe.
- •Runs project-defined scripts via `bun run lint`, `bun run typecheck`, and `bun test`, which can execute arbitrary repository code.
- •Runs `git push -u origin <branch>` and `gh pr create`, which modify remote state and may require authenticated network access.
- •Assumes `main` is the base branch and may produce incorrect diffs/PR context in repos using another default branch.
Examples
Open a pull request for my current branch against main.Run the pre-flight checks and open a PR with a conventional title and a summary/test plan for this feature branch.My branch isn't pushed yet — push it upstream and create the pull request with a structured description.name: pr version: 1.0.0 description: Open a pull request with conventional title, structured description, and pre-flight checks. triggers:
- pr
- pull request
- open pr allowed-tools:
- Bash
- Read
PR Skill
Open a pull request for the current branch with proper conventions.
Step 1 — Pre-flight checks
Run these in parallel and report results:
bun run lint
bun run typecheck
bun test
If any fail, show the errors and ask the user whether to proceed or fix first.
Step 2 — Gather context
Run these to understand the branch:
git branch --show-current— current branch namegit log main..HEAD --oneline— commits on this branchgit diff main..HEAD --stat— files changed
Step 3 — Determine PR title
The PR title must be a conventional commit format: <type>(<scope>): <description>
Pick type and scope the same way as the /commit skill, but based on the overall branch intent (not individual commits).
Step 4 — Write PR description
Use this structure:
## Summary
- Bullet 1: what changed and why
- Bullet 2: key design decisions
- Bullet 3: anything reviewers should pay attention to
## Test plan
- [ ] Tests pass locally
- [ ] Specific scenario tested
Step 5 — Check remote
Run git remote -v and git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null to check if the branch is pushed.
If not pushed, run git push -u origin <branch>.
Step 6 — Create PR
gh pr create --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
Show the PR URL to the user when done.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/open-a-pull-request-with-conventions-mryiqfjo/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/open-a-pull-request-with-conventions-mryiqfjo' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/open-a-pull-request-with-conventions-mryiqfjo/download' --output '.skill-downloads/open-a-pull-request-with-conventions-mryiqfjo/SKILL.md.part' && mv '.skill-downloads/open-a-pull-request-with-conventions-mryiqfjo/SKILL.md.part' '.skill-downloads/open-a-pull-request-with-conventions-mryiqfjo/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/open-a-pull-request-with-conventions-mryiqfjo/SKILL.md' && test -s '.skill-downloads/open-a-pull-request-with-conventions-mryiqfjo/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr' && cp -R '.skill-downloads/open-a-pull-request-with-conventions-mryiqfjo' '.claude/skills/pr'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/open-a-pull-request-with-conventions-mryiqfjo'openskills read 'open-a-pull-request-with-conventions-mryiqfjo'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/open-a-pull-request-with-conventions-mryiqfjo/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.