PR Finalize Review
microsoft/garnet
Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.
Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style.
Install Gh PR Metadata
$ npx skills add module-federation/core --skill gh-pr-metadata -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install module-federation/core gh-pr-metadata --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/module-federation/core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/gh-pr-metadata .claude/skills/gh-pr-metadata && 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 "gh-pr-metadata" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/gh-pr-metadata into .claude/skills/gh-pr-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-pr-metadata", 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/module-federation/core/tree/main/.codex/skills/gh-pr-metadataType 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 module-federation/core --skill gh-pr-metadata -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install module-federation/core gh-pr-metadata --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/gh-pr-metadata .agents/skills/gh-pr-metadata && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gh-pr-metadata" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/gh-pr-metadata into .agents/skills/gh-pr-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-pr-metadata", 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 module-federation/core --skill gh-pr-metadata -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install module-federation/core gh-pr-metadata --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/gh-pr-metadata .cursor/skills/gh-pr-metadata && 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 "gh-pr-metadata" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/gh-pr-metadata into .cursor/skills/gh-pr-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-pr-metadata", 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/module-federation/core.git --path .codex/skills/gh-pr-metadata--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 module-federation/core --skill gh-pr-metadata -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install module-federation/core gh-pr-metadata --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/gh-pr-metadata .gemini/skills/gh-pr-metadata && 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 "gh-pr-metadata" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/gh-pr-metadata into .gemini/skills/gh-pr-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-pr-metadata", 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 module-federation/core gh-pr-metadataInstalls 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 module-federation/core --skill gh-pr-metadata -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/gh-pr-metadata .github/skills/gh-pr-metadata && 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 "gh-pr-metadata" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/gh-pr-metadata into .github/skills/gh-pr-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-pr-metadata", 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 module-federation/core --skill gh-pr-metadata -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install module-federation/core gh-pr-metadata --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/gh-pr-metadata .opencode/skills/gh-pr-metadata && 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 "gh-pr-metadata" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/gh-pr-metadata into .opencode/skills/gh-pr-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-pr-metadata", 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
gh-pr-metadata- GitHub stars
- 2.7k
- Token cost
- ~1k tokens
- SKILL.md length
- 440 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style.
- Works in 2 steps: Resolve the current branch PR. → Inspect the current branch state against…
- A PR title is vague
- SKILL.md covers Overview, Workflow, Body Guidance and Title Guidance, plus 1 more section
- Runs Python scripts from its folder; calls git, python3 and gh
What it does
Gh PR Metadata is an agent skill from module-federation/core. Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style. Use when a PR title is vague or misformatted, when the PR body is missing required sections or checklist items, when Codex needs to normalize PR metadata before review or merge, or when GitHub comments/checks indicate the PR title or body should be corrected.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/repo-pr-format.md` and `scripts/validate_pr_metadata.py`).
It sits in Development, covering Pull requests and Commit messages. It works with GitHub. The repository describes itself as: Module Federation is a concept that allows developers to share code and resources across multiple JavaScript applications. The licence is MIT.
When your agent uses it
- A PR title is vague
- The PR body is missing required sections
- Checklist items
- Codex needs to normalize PR metadata before review
Example prompts
- “/gh-pr-metadata”
Requirements
- Python 3
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Resolve the current branch PR.
- Inspect the current branch state against the PR base branch.
What it can do on your machine
Read from SKILL.md and the folder at commit d139eed. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
gitpython3gh
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
Gh PR Metadata loads about 1k tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 440 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); the scripts in this folder are not scanned.
SKILL.md
The full file from module-federation/core at commit d139eed, republished under its MIT licence (© module-federation). 440 words, ~1,017 tokens.
Download SKILL.mdSave it as
.claude/skills/gh-pr-metadata/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- gh-pr-metadata
- description
- Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style. Use when a PR title is vague or misformatted, when the PR body is missing required sections or checklist items, when Codex needs to normalize PR metadata before review or merge, or when GitHub comments/checks indicate the PR title or body should be corrected.
GH PR Metadata
Overview
Normalize the current branch's GitHub PR metadata to this repo's expectations. Keep the title in conventional-commit style, keep the body aligned to .github/pull_request_template.md, and validate before handoff.
Ground the PR metadata in the live branch state, not stale branch names or old commit subjects. Always inspect the current branch diff versus its base before rewriting the PR title/body.
Read references/repo-pr-format.md when you need the exact section order, checklist items, or a title example.
Workflow
- Resolve the current branch PR.
gh pr view --json number,title,body,url,headRefName,baseRefName- Inspect the current branch state against the PR base branch.
At minimum, check:
git diff --name-status origin/<base>...HEAD
git diff --stat origin/<base>...HEAD
git log --oneline --decorate --no-merges origin/<base>..HEADUse these to answer:
- what files actually differ from the base right now
- which changes are functional versus cleanup/tooling/docs
- whether the existing PR title/body still matches the current branch after rebases, reverts, or scope narrowing
- Validate the current title and body.
python3 .codex/skills/gh-pr-metadata/scripts/validate_pr_metadata.py- If the PR body needs a clean template scaffold, print one:
python3 .codex/skills/gh-pr-metadata/scripts/validate_pr_metadata.py --print-template- Rewrite the PR title in conventional-commit style.
Rules:
- Prefer
type(scope): summary - Keep the title short and direct
- Use repo-typical types such as
fix,feat,docs,refactor,chore,test,ci,build,perf,revert - Keep the scope tight to the affected package or subsystem when useful
- Do not add prefixes like
[codex] - Make sure the title describes the current branch diff, not the original branch intent if the branch was later narrowed or partially reverted
- Rewrite the PR body to preserve the repo template structure:
## Description## Related Issue## Types of changes## Checklist
- Update the PR with
gh.
Prefer writing the body to a temporary file first, then:
gh pr edit --title "<new-title>" --body-file /tmp/pr-body.md- Re-run validation and report whether the PR metadata is now compliant.
python3 .codex/skills/gh-pr-metadata/scripts/validate_pr_metadata.pyShow full SKILL.md (168 more words)Show less
Body Guidance
- Keep
Descriptionprose-first and specific to the branch. - Reflect the branch as it exists now, especially after rebases, cleanups, or partial reverts.
- Summarize the real file-level themes from the live diff instead of copying commit messages mechanically.
- Put issue references in
Related Issue; if there is no issue, say so plainly instead of deleting the section. - In
Types of changes, check only the boxes that actually apply. - In
Checklist, preserve all repo checklist items and mark only the items that are true. - Do not remove required sections just because the PR is small.
- Keep the body concise; do not turn it into a changelog dump.
Title Guidance
Good examples:
fix(node): normalize remote chunk parsingchore(manifest): drop extra compat cleanupdocs(agents): prefer normalized webpack path requires
Bad examples:
update prfix stuff[codex] cleanup
Validation
Use the helper script to detect:
- non-conventional PR titles
- missing or reordered template sections
- missing repo checklist items
The script validates either the current PR from gh or explicit --title / --body-file input.
© module-federation, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references) in .codex/skills/gh-pr-metadata of module-federation/core.
- SKILL.md
- agents/openai.yaml
- references/repo-pr-format.md
- scripts/validate_pr_metadata.py
Open the folder on GitHubat commit d139eed
Compare with similar skills
Gh PR Metadata 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 |
|---|---|---|---|---|---|---|
| Gh PR Metadata this skillmodule-federation/core | 2.7k | — | ~1k | Automated safety check: Pass | MIT | |
| PR Finalize Reviewmicrosoft/garnet | 12k | — | ~3.1k | Automated safety check: Pass | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 | |
| Submit PRtisfeng/Easydict | 15k | — | ~595 | Automated safety check: Pass | GPL-3.0 |
Similar skills
- Official
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.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
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.
Submit PR
tisfeng/Easydict
创建或复用当前 checkout 已提交变更的 GitHub PR，必要时推送任务分支。PR 审查使用 review-pr；仅本地提交使用 git-commit。
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.
More from module-federation/core
Changeset PR
module-federation/core
Create or update a .changeset/.md file for the current branch or PR in this repository, choose the correct package scope and release type, and verify the result against repo-specific Changesets…
Local CI
module-federation/core
Run this repository's local CI parity commands and pnpm run ci:local jobs.
Sokra Mode
module-federation/core
Design, build, and maintain module-federation/core the way sokra (Tobias Koppers) built webpack 5: plugin architecture, container/sharing, runtime, caching, and reviews.
Sokra Mode
module-federation/core
Apply sokra's webpack design discipline to module-federation/core plugin architecture, runtime, caching, and reviews when asked for sokra mode or to review or build something like sokra would.
Related
Works with
Categories
Questions about Gh PR Metadata
What does Gh PR Metadata do?
Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style. Gh PR Metadata is an agent skill from module-federation/core. Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style.
When should I use Gh PR Metadata?
Gh PR Metadata fits situations like: A PR title is vague; the PR body is missing required sections; checklist items; Codex needs to normalize PR metadata before review.
How do I install Gh PR Metadata in Claude Code?
Run `npx skills add module-federation/core --skill gh-pr-metadata -a claude-code`. Or copy the skill folder (.codex/skills/gh-pr-metadata in module-federation/core) into .claude/skills/gh-pr-metadata in your project. Claude Code loads it when a task matches its description.
How do I install Gh PR Metadata in Codex?
Run `npx skills add module-federation/core --skill gh-pr-metadata -a codex`. Or copy the skill folder (.codex/skills/gh-pr-metadata in module-federation/core) into .agents/skills/gh-pr-metadata in your project. Codex loads it when a task matches its description.
Can I use Gh PR Metadata 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 module-federation/core --skill gh-pr-metadata -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gh-pr-metadata, .gemini/skills/gh-pr-metadata, .github/skills/gh-pr-metadata and .opencode/skills/gh-pr-metadata in your project.
What does Gh PR Metadata need to run?
Going by SKILL.md and its folder, Gh PR Metadata needs Python for the scripts in its folder and the command-line tools its instructions call (git, python3 and gh). Our summary lists: Python 3.
Does Gh PR Metadata 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 Gh PR Metadata 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Gh PR Metadata use?
Gh PR Metadata 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 Gh PR Metadata use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 254 tokens, read only when the agent opens those files.
What are the alternatives to Gh PR Metadata?
Skills that share tags, products or a category with Gh PR Metadata: PR Finalize Review (microsoft/garnet, 12k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gh PR Metadata?
module-federation (a GitHub organization) maintains it in module-federation/core, which has 2,655 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.
Source: module-federation/core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.