React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Analyzes git branch diffs (added, modified, deleted files) against the default or target branch, and generates a conventional commit title, PR title, and formatted markdown PR description for…
Install PR Preparer
$ npx skills add flutter-ml/google_ml_kit_flutter --skill pr-preparer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install flutter-ml/google_ml_kit_flutter pr-preparer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/flutter-ml/google_ml_kit_flutter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr_preparer .claude/skills/pr-preparer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pr-preparer" agent skill from https://github.com/flutter-ml/google_ml_kit_flutter/tree/develop/.agents/skills/pr_preparer into .claude/skills/pr-preparer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-preparer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/flutter-ml/google_ml_kit_flutter/tree/develop/.agents/skills/pr_preparerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add flutter-ml/google_ml_kit_flutter --skill pr-preparer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install flutter-ml/google_ml_kit_flutter pr-preparer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter-ml/google_ml_kit_flutter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pr_preparer .agents/skills/pr-preparer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pr-preparer" agent skill from https://github.com/flutter-ml/google_ml_kit_flutter/tree/develop/.agents/skills/pr_preparer into .agents/skills/pr-preparer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-preparer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flutter-ml/google_ml_kit_flutter --skill pr-preparer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install flutter-ml/google_ml_kit_flutter pr-preparer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter-ml/google_ml_kit_flutter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pr_preparer .cursor/skills/pr-preparer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pr-preparer" agent skill from https://github.com/flutter-ml/google_ml_kit_flutter/tree/develop/.agents/skills/pr_preparer into .cursor/skills/pr-preparer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-preparer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/flutter-ml/google_ml_kit_flutter.git --path .agents/skills/pr_preparer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add flutter-ml/google_ml_kit_flutter --skill pr-preparer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install flutter-ml/google_ml_kit_flutter pr-preparer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter-ml/google_ml_kit_flutter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pr_preparer .gemini/skills/pr-preparer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pr-preparer" agent skill from https://github.com/flutter-ml/google_ml_kit_flutter/tree/develop/.agents/skills/pr_preparer into .gemini/skills/pr-preparer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-preparer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install flutter-ml/google_ml_kit_flutter pr-preparerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add flutter-ml/google_ml_kit_flutter --skill pr-preparer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/flutter-ml/google_ml_kit_flutter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pr_preparer .github/skills/pr-preparer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pr-preparer" agent skill from https://github.com/flutter-ml/google_ml_kit_flutter/tree/develop/.agents/skills/pr_preparer into .github/skills/pr-preparer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-preparer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flutter-ml/google_ml_kit_flutter --skill pr-preparer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install flutter-ml/google_ml_kit_flutter pr-preparer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter-ml/google_ml_kit_flutter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pr_preparer .opencode/skills/pr-preparer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pr-preparer" agent skill from https://github.com/flutter-ml/google_ml_kit_flutter/tree/develop/.agents/skills/pr_preparer into .opencode/skills/pr-preparer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-preparer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pr-preparer- GitHub stars
- 1.3k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 352 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyzes git branch diffs (added, modified, deleted files) against the default or target branch, and generates a conventional commit title, PR title, and formatted markdown PR description for…
- Works in 3 steps: Determine the Base Branch & Diff Scope → Analyze Code Changes → Format Conventional Commit & PR Details
- The user asks to prepare a PR
- SKILL.md covers Workflow Steps and Guidelines & Best Practices
- Calls git and gh
What it does
PR Preparer is an agent skill from flutter-ml/google_ml_kit_flutter. Analyzes git branch diffs (added, modified, deleted files) against the default or target branch, and generates a conventional commit title, PR title, and formatted markdown PR description for copy-pasting to GitHub. Use when the user asks to prepare a PR, generate a PR description, generate a commit message, summarize branch changes, or create a PR template.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Commit messages, Pull requests and Git workflow. It works with GitHub. The repository describes itself as: A flutter plugin that implements Google's standalone ML Kit. The licence is MIT.
When your agent uses it
- The user asks to prepare a PR
- Generate a PR description
- Generate a commit message
- Summarize branch changes
Example prompts
- “Use the pr-preparer skill to analyz git branch diffs (added, modified, deleted files) against the default or target branch, and generates a…”
- “/pr-preparer”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1083593. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
PR Preparer loads about 1.2k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 352 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from flutter-ml/google_ml_kit_flutter at commit 1083593, republished under its MIT licence (© flutter-ml). 352 words, ~1,215 tokens.
Download SKILL.mdSave it as
.claude/skills/pr-preparer/SKILL.md (or your agent's skills folder).- name
- pr-preparer
- description
- Analyzes git branch diffs (added, modified, deleted files) against the default or target branch, and generates a conventional commit title, PR title, and formatted markdown PR description for copy-pasting to GitHub. Use when the user asks to prepare a PR, generate a PR description, generate a commit message, summarize branch changes, or create a PR template.
PR Preparer Skill
This skill guides the AI assistant in comparing the current branch against the base/default branch (develop, main, master), analyzing all added, modified, and deleted files, and generating a conventional commit title, PR title, and a comprehensive, GitHub-ready markdown PR description.
Workflow Steps
Step 1: Determine the Base Branch & Diff Scope
- Identify the current branch and default target branch:
bash CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD) BASE_BRANCH=$(gh pr view --json baseRefName --jq '.baseRefName' 2>/dev/null || git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@refs/remotes/origin/@@' || echo "develop") - Empty Diff & Branch Validation Check:
Run a diff check against
$BASE_BRANCHand working directory:bash BRANCH_DIFF=$(git diff --name-only "$BASE_BRANCH"...HEAD) WORKING_DIFF=$(git status -s)Case A: Zero changes anywhere (branch is identical to base & working tree is clean):
- Notify the user:
markdown ℹ️ No changes detected on branch `<CURRENT_BRANCH>` compared to `<BASE_BRANCH>`. Please make code edits or switch to a branch with changes before running PR preparation. - Exit early without generating a PR description.
- Notify the user:
Case B: Same branch or uncommitted-only changes:
- If
CURRENT_BRANCH == BASE_BRANCHorBRANCH_DIFFis empty, butWORKING_DIFFhas local edits, analyze uncommitted changes againstHEAD:bash git diff HEAD git status -s
- If
Case C: Feature branch with committed changes (Standard Flow):
- Compare branch changes against
$BASE_BRANCH:bash git diff --stat "$BASE_BRANCH"...HEAD git status -s
- Compare branch changes against
Show full SKILL.md (168 more words)Show less
Step 2: Analyze Code Changes
Fetch detailed diffs to understand the scope and intent of all changes:
bash git diff "$BASE_BRANCH"...HEADCategorize all changed files:
- 🟢 Added (
[NEW]): Newly created files, modules, scripts, or tests. - 🟡 Modified (
[MODIFY]): Updated configuration, refactored logic, schema edits, or updated docs. - 🔴 Deleted (
[DELETE]): Removed obsolete files, dead code, or redundant scripts.
- 🟢 Added (
Identify key themes and impact:
- Architecture & logic changes.
- Dependency or configuration updates.
- CI/CD workflow modifications.
- Database migrations or schema updates.
- Documentation adjustments.
Step 3: Format Conventional Commit & PR Details
Generate output with clear separation between titles and description, using formatted markdown blocks for easy one-click copy/pasting.
Format Template:
### 📝 Conventional Commit Title
```text
<type>(<scope>): <short imperative summary in lower case, max 72 chars>
```
---
### 🔤 Pull Request Title
```text
<Type>: <Capitalized Concise Description of PR Goal>
```
---
### 📄 Pull Request Description
```markdown
## 📌 Overview
<Brief 2-3 sentence overview explaining the problem, context, and what this PR accomplishes.>
---
## 🛠 Key Changes
### [Component / Feature Area 1]
- 🟢 `path/to/new_file`: Brief description of what was added.
- 🟡 `path/to/modified_file`: Brief description of what changed.
### [Component / Feature Area 2]
- 🔴 `path/to/deleted_file`: Brief description of why this file was removed.
---
## 🧪 Verification & Testing
- [x] Ran unit tests: `uv run python manage.py test --settings=besties_backend.test_settings_sqlite`
- [x] Ran linters/pre-commit: `uv run pre-commit run --all-files`
- [x] Manual verification steps performed.
---
## ⚠️ Notes & Risk Assessment
- **Breaking Changes:** None / <List breaking changes if any>
- **Migration Required:** No / Yes (`python manage.py migrate`)
- **Environment Variables:** No new env vars required / <List new env vars>
```Guidelines & Best Practices
- Conventional Commit Types: Use
feat,fix,refactor,chore,docs,test,ci, orstyle. - Imperative Mood: Use imperative present tense in titles ("add feature" instead of "added feature").
- Concise Summaries: Group individual file changes by logical component (e.g., API, Database, CI/CD, Documentation) rather than listing random files.
- Copy/Paste Friendly: Always enclose output in markdown fenced code blocks (
```textand```markdown).
© flutter-ml, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/pr_preparer of flutter-ml/google_ml_kit_flutter.
Open the folder on GitHubat commit 1083593
Compare with similar skills
PR Preparer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| PR Preparer this skillflutter-ml/google_ml_kit_flutter | 1.3k | — | ~1.2k | Automated safety check: Pass | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 | |
| Codewhale Landing Workflowcodewhale-hq/Codewhale | 41k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Publish Pull Request for taskctltaskctl/taskctl | 434 | — | ~979 | Automated safety check: Pass | GPL-3.0 | |
| Git GitHub Opsc5inco/compose-pokedexer | 143 | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
Codewhale Landing Workflow
codewhale-hq/Codewhale
Decides how verified work should reach main, directly, in a worktree or on an integration branch, while keeping contributor credit and respecting merge gates.
Publish Pull Request for taskctl
taskctl/taskctl
Publishes the current branch and opens or updates a GitHub pull request for the taskctl repo, after a pre-publish gate and with a description template matched to the change.
Git GitHub Ops
c5inco/compose-pokedexer
Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs.
Pull Request Creation
lobehub/lobehub
Creates a pull request for the current branch against canary, or splits a cross-layer branch into ordered stacked PRs so backend changes merge before their callers.
More from flutter-ml/google_ml_kit_flutter
PR Comment Handler
flutter-ml/google_ml_kit_flutter
Fetches unresolved pull request comments using the GitHub CLI (gh), addresses feedback in the codebase, and formats markdown replies for easy copy-pasting to GitHub PRs.
Related
Works with
Categories
Questions about PR Preparer
What does PR Preparer do?
Analyzes git branch diffs (added, modified, deleted files) against the default or target branch, and generates a conventional commit title, PR title, and formatted markdown PR description for…. PR Preparer is an agent skill from flutter-ml/google_ml_kit_flutter. Analyzes git branch diffs (added, modified, deleted files) against the default or target branch, and generates a conventional commit title, PR title, and formatted markdown PR description for copy-pasting to GitHub.
When should I use PR Preparer?
PR Preparer fits situations like: the user asks to prepare a PR; generate a PR description; generate a commit message; summarize branch changes.
How do I install PR Preparer in Claude Code?
Run `npx skills add flutter-ml/google_ml_kit_flutter --skill pr-preparer -a claude-code`. Or copy the skill folder (.agents/skills/pr_preparer in flutter-ml/google_ml_kit_flutter) into .claude/skills/pr-preparer in your project. Claude Code loads it when a task matches its description.
How do I install PR Preparer in Codex?
Run `npx skills add flutter-ml/google_ml_kit_flutter --skill pr-preparer -a codex`. Or copy the skill folder (.agents/skills/pr_preparer in flutter-ml/google_ml_kit_flutter) into .agents/skills/pr-preparer in your project. Codex loads it when a task matches its description.
Can I use PR Preparer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flutter-ml/google_ml_kit_flutter --skill pr-preparer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-preparer, .gemini/skills/pr-preparer, .github/skills/pr-preparer and .opencode/skills/pr-preparer in your project.
What does PR Preparer need to run?
Going by SKILL.md and its folder, PR Preparer needs the command-line tools its instructions call (git and gh). Our summary lists: Python 3.
Does PR Preparer access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is PR Preparer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does PR Preparer use?
PR Preparer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does PR Preparer use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to PR Preparer?
Skills that share tags, products or a category with PR Preparer: React Router Pull Request Creator (remix-run/react-router, 57k stars), Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars), Codewhale Landing Workflow (codewhale-hq/Codewhale, 41k stars) and Publish Pull Request for taskctl (taskctl/taskctl, 434 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PR Preparer?
flutter-ml (a GitHub organization) maintains it in flutter-ml/google_ml_kit_flutter, which has 1,284 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 14, 2026.
Source: flutter-ml/google_ml_kit_flutter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.