Automated summary
Reads the current branch diff against origin/main and prints a PR title and body in chat that follow the repo's pull request template, without pushing or creating the PR.
Strengths
- Reuses .github/pull_request_template.md verbatim rather than inventing a body structure
- Produces a conventional-commit-style title, picking the dominant type when commits are mixed
- Only ticks checklist items actually verified this session and explicitly flags a missing issue number instead of guessing
- Outputs title and body separately, with the body in a fenced block ready to paste into gh pr create --body
Limitations
- Assumes a specific repository (dynamic-neural-field-composer) and a hardcoded origin/main base branch
- Does not push or open the PR, so the user must copy-paste the output manually
- The checklist references repo-specific items (Doxygen, wiki, multi-OS CI) the skill cannot verify on its own
- Limited handling of edge cases beyond stopping when the branch is main or has no commits ahead
Use it when you want a draft PR title and description aligned with the repo's template, without actually opening the PR.
Avoid it on repos with no pull_request_template.md or origin/main remote, or when you expect the PR to be created for you.
Security analysis
SafeThe skill is purely read-only: it runs `git branch`, `git log`, `git diff` against origin/main and prints a formatted PR title/body to chat. It explicitly forbids `git push` and `gh pr create`, touches no secrets, makes no network calls, and performs no filesystem writes or destructive operations. Execution risk is negligible.
No concerns found
How this analysis is madeExamples
Write the PR title and description for my current branch.What should the PR say? Fill in the repo's pull request template for this branch.Suggest a conventional-commit-style PR title and body for the diff against origin/main.name: pr description: Read the branch diff in dynamic-neural-field-composer and print a PR title and description in chat, filling the repo's pull request template. Use when asked to write, draft or suggest a PR title/description, or "what should the PR say".
PR
Reads the branch against origin/main and prints a PR title and body to chat. Never runs
gh pr create or git push - opening the PR stays a human decision.
1. Read the branch
git branch --show-current
git log origin/main..HEAD --oneline
git diff origin/main...HEAD --stat
If the branch is main, or there are no commits ahead of origin/main, say so and stop.
2. Title
Same conventional format as a commit - <type>: <lowercase summary>. If the branch's
commits share one type, use it; if they are mixed, pick the dominant concern rather than
concatenating types.
3. Body - fill the existing template
Use .github/pull_request_template.md verbatim as the shape. Do not invent a different
body structure.
## What and why
<2-4 bullets or a short paragraph - what changed, why>
## How to verify
<concrete steps - commands, a named test filter, the `build-and-test` skill>
## Checklist
- [ ] Tests added or updated
- [ ] Doxygen updated (if public API changed)
- [ ] Wiki updated (if user-visible behaviour changed)
- [ ] CI passes (Windows, Linux, macOS)
Tick a checklist box only if it was actually verified this session. Leave the rest unticked - do not tick optimistically.
4. Issue number
Look for it in the branch slug or the commit messages. If found, close the body with
Closes #<N>. If not found, do not guess a number - emit the literal placeholder
Closes #<N> and say in your reply that no issue number was found.
Output
A markdown title line, kept outside the fence since gh pr create takes --title and
--body as separate arguments, followed by the filled body inside its own single fenced
code block (```markdown) so the body renders as literal, copy-pasteable text rather
than being rendered as chat formatting - ready to paste into gh pr create --body.
Nothing else - no push, no gh pr create.
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/draft-a-pr-title-and-description-mvda86ol/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/draft-a-pr-title-and-description-mvda86ol' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/draft-a-pr-title-and-description-mvda86ol/download' --output '.skill-downloads/draft-a-pr-title-and-description-mvda86ol/SKILL.md.part' && mv '.skill-downloads/draft-a-pr-title-and-description-mvda86ol/SKILL.md.part' '.skill-downloads/draft-a-pr-title-and-description-mvda86ol/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/draft-a-pr-title-and-description-mvda86ol/SKILL.md' && test -s '.skill-downloads/draft-a-pr-title-and-description-mvda86ol/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr' && cp -R '.skill-downloads/draft-a-pr-title-and-description-mvda86ol' '.claude/skills/pr'Cursor
test -f '.skill-downloads/draft-a-pr-title-and-description-mvda86ol/SKILL.md' && test -s '.skill-downloads/draft-a-pr-title-and-description-mvda86ol/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/pr' && cp -R '.skill-downloads/draft-a-pr-title-and-description-mvda86ol' '.cursor/skills/pr'Codex
test -f '.skill-downloads/draft-a-pr-title-and-description-mvda86ol/SKILL.md' && test -s '.skill-downloads/draft-a-pr-title-and-description-mvda86ol/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/pr' && cp -R '.skill-downloads/draft-a-pr-title-and-description-mvda86ol' '.agents/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/draft-a-pr-title-and-description-mvda86ol'openskills read 'draft-a-pr-title-and-description-mvda86ol'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/draft-a-pr-title-and-description-mvda86ol/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.