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.
Write commit messages, PR titles/descriptions, and GitHub comments with a user-first style; apply release-drafter-compatible labels; produce release-note-ready PR titles.
Install PR And Commit Writing
$ npx skills add PSBrew/MkPFS --skill pr-and-commit-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PSBrew/MkPFS pr-and-commit-writing --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/PSBrew/MkPFS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pr-and-commit-writing .claude/skills/pr-and-commit-writing && 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-and-commit-writing" agent skill from https://github.com/PSBrew/MkPFS/tree/main/.claude/skills/pr-and-commit-writing into .claude/skills/pr-and-commit-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-and-commit-writing", 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/PSBrew/MkPFS/tree/main/.claude/skills/pr-and-commit-writingType 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 PSBrew/MkPFS --skill pr-and-commit-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PSBrew/MkPFS pr-and-commit-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PSBrew/MkPFS.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/pr-and-commit-writing .agents/skills/pr-and-commit-writing && 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-and-commit-writing" agent skill from https://github.com/PSBrew/MkPFS/tree/main/.claude/skills/pr-and-commit-writing into .agents/skills/pr-and-commit-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-and-commit-writing", 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 PSBrew/MkPFS --skill pr-and-commit-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PSBrew/MkPFS pr-and-commit-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PSBrew/MkPFS.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/pr-and-commit-writing .cursor/skills/pr-and-commit-writing && 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-and-commit-writing" agent skill from https://github.com/PSBrew/MkPFS/tree/main/.claude/skills/pr-and-commit-writing into .cursor/skills/pr-and-commit-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-and-commit-writing", 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/PSBrew/MkPFS.git --path .claude/skills/pr-and-commit-writing--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 PSBrew/MkPFS --skill pr-and-commit-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PSBrew/MkPFS pr-and-commit-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PSBrew/MkPFS.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/pr-and-commit-writing .gemini/skills/pr-and-commit-writing && 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-and-commit-writing" agent skill from https://github.com/PSBrew/MkPFS/tree/main/.claude/skills/pr-and-commit-writing into .gemini/skills/pr-and-commit-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-and-commit-writing", 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 PSBrew/MkPFS pr-and-commit-writingInstalls 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 PSBrew/MkPFS --skill pr-and-commit-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PSBrew/MkPFS.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/pr-and-commit-writing .github/skills/pr-and-commit-writing && 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-and-commit-writing" agent skill from https://github.com/PSBrew/MkPFS/tree/main/.claude/skills/pr-and-commit-writing into .github/skills/pr-and-commit-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-and-commit-writing", 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 PSBrew/MkPFS --skill pr-and-commit-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PSBrew/MkPFS pr-and-commit-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PSBrew/MkPFS.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/pr-and-commit-writing .opencode/skills/pr-and-commit-writing && 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-and-commit-writing" agent skill from https://github.com/PSBrew/MkPFS/tree/main/.claude/skills/pr-and-commit-writing into .opencode/skills/pr-and-commit-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-and-commit-writing", 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-and-commit-writing- GitHub stars
- 174
- Token cost
- ~910 tokens
- SKILL.md length
- 356 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Write commit messages, PR titles/descriptions, and GitHub comments with a user-first style; apply release-drafter-compatible labels; produce release-note-ready PR titles.
- Works in 4 steps: Short, natural-language title (≤50… → Focus on the user-facing problem solved;… → Blank line between title and body. → …
- Tasks that involve Commit messages
- SKILL.md covers Goal, Commit message rules, PR title rules and PR description rules, plus 3 more sections
- Calls gh and make
What it does
PR And Commit Writing is an agent skill from PSBrew/MkPFS. Write commit messages, PR titles/descriptions, and GitHub comments with a user-first style; apply release-drafter-compatible labels; produce release-note-ready PR titles.
Its SKILL.md is about 910 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 and Changelog and release notes. It works with GitHub. The repository describes itself as: Create and Manage Unsigned PFS (Playstation File System) image files with file compression and checksum support. The licence is GPL-3.0.
When your agent uses it
- Tasks that involve Commit messages
- Tasks that involve Changelog and release notes
Example prompts
- “/pr-and-commit-writing”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Short, natural-language title (≤50 chars). Emoji optional.
- Focus on the user-facing problem solved; avoid deep implementation details.
- Blank line between title and body.
- Optional body: concise (wrap ~72 cols), user-visible problem + high-level change.
What it can do on your machine
Read from SKILL.md and the folder at commit 1d5df56. 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:
ghmake
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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 And Commit Writing loads about 910 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 356 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 PSBrew/MkPFS at commit 1d5df56, republished under its GPL-3.0 licence (© PSBrew). 356 words, ~910 tokens.
Download SKILL.mdSave it as
.claude/skills/pr-and-commit-writing/SKILL.md (or your agent's skills folder).- name
- pr-and-commit-writing
- description
- Write commit messages, PR titles/descriptions, and GitHub comments with a user-first style; apply release-drafter-compatible labels; produce release-note-ready PR titles.
- context
- fork
Writing PRs, commit messages, and GitHub comments
Use whenever you need to: create/edit a PR, write a public commit message, write/edit a GitHub comment, or assign labels/tags to a PR.
Goal
Write public-facing GitHub content for non-technical readers first. Keep everything short, friendly, scannable, and focused on the user problem solved.
Commit message rules
- Short, natural-language title (≤50 chars). Emoji optional.
- Focus on the user-facing problem solved; avoid deep implementation details.
- Blank line between title and body.
- Optional body: concise (wrap ~72 cols), user-visible problem + high-level change.
Example:
Avoid broken inner filenames by removing special characters
Some consoles could not mount images when inner filenames had special characters.
This change sanitizes the internal filename, prefers title IDs, and warns when names are changed.
Verification still works even when external and internal names differ.PR title rules
- One short sentence (≤72 chars), plain language, user-facing.
- Describe the problem solved or user impact; avoid implementation details.
- No Conventional Commit prefixes (no
feat:,fix:, etc.). No emoji. - Titles should paste directly into release notes.
Good examples:
Fix inner image names that break mountsMake single-file image names saferUpdate the documentation about the verify command
PR description rules
Use UTF-8 icons and Markdown.
# Fix inner image names that break mounts
## 🤔 Why?
- Explain the user-visible problem in plain language.
## 🔧 What changed
- 3-5 short bullets. Focus on behavior, not internal code structure.
## 🧪 How to test
- One short command or simple manual flow.
- Link related issues (e.g., Closes #123).
## 💬 Notes for non-technical readers
- Reassure the reader what changed and what did not change.Writing guidance
- Use emoji lightly for scanning: ✅ 🔧 🧪 🤔 💬 ⚠️ 📦.
- Bullets over dense prose. Speak like you're updating a non-technical maintainer.
- Always state the original problem clearly in Why?.
- If contents are unchanged and only metadata/filenames changed, say so explicitly.
- Never mention AI tools or attribute text to any AI tool.
- Clean up PII, local paths, or internal-only details.
Show full SKILL.md (137 more words)Show less
Labels and tags
Use labels that fit .github/release-drafter-config.yml. Pick one primary:
feature— new user-facing capabilitybug— user-visible fixmaintenance— cleanup, tooling, refactordocumentation— docs-only changedependencies— dependency updatesecurity— security fixbreaking— breaking change
Other: skip-changelog only when the PR should not appear in release notes.
Choose based on user impact first, then implementation details.
GitHub CLI notes
gh pr edit .../gh pr create ...GH_PAGER=cat gh pr edit <number> --add-label "bug"
Final checklist
- PR title release-note ready (plain sentence, ≤72 chars, no CC prefixes, no emoji)
- Text explains the problem first; clear Why? section for PRs
- UTF-8 icons used lightly; language understandable to non-technical readers
- Correct label applied;
skip-changelogif needed - Related issues linked (e.g., Closes #123)
- No AI attribution; no PII/local paths
- After editing with
gh, re-read the published PR to confirm it matches this skill
© PSBrew, GPL-3.0. 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 .claude/skills/pr-and-commit-writing of PSBrew/MkPFS.
Open the folder on GitHubat commit 1d5df56
Compare with similar skills
PR And Commit Writing 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 And Commit Writing this skillPSBrew/MkPFS | 174 | — | ~910 | Automated safety check: Pass | GPL-3.0 | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Plane Release Notes Generatormakeplane/plane | 61k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| Chinese Commit ConventionsjnMetaCode/superpowers-zh | 8.3k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Release Minorknuckleswtf/scribe | 2.3k | — | ~437 | Automated safety check: Pass | MIT | |
| Release NotesEvilBeaver/OneScript | 587 | — | ~779 | Automated safety check: Pass | MPL-2.0 |
Similar skills
Plane Release Notes Generator
makeplane/plane
Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.
Chinese Commit Conventions
jnMetaCode/superpowers-zh
Reference for Chinese-language git commits and changelogs: Conventional Commits adapted for Chinese teams, with templates, breaking-change notes and issue links for several platforms.
Release Minor
knuckleswtf/scribe
Automates the process of tagging a new minor release for Scribe by analyzing commit messages, updating the changelog, and creating a GitHub release.
Release Notes
EvilBeaver/OneScript
This skill creates release notes for new release by reading git commit log.
Release Workflow
Caldis/react-zmage
A skill your agent uses when the user wants to ship a new version of react-zmage to npm.
More from PSBrew/MkPFS
HTML Report Builder
PSBrew/MkPFS
Build a self-contained HTML report as a companion artifact for audits, verifications, research, or long multi-command investigations.
Related Projects Index
PSBrew/MkPFS
Compact index of upstream projects and reference sources relevant to PKG/PFS/exFAT research.
Related Project Add
PSBrew/MkPFS
Add a new related project or reference source to the Related Projects index.
Running Unit Tests
PSBrew/MkPFS
Run formatting, linting, and tests; then iteratively fix failures until the branch is green.
Related
Works with
Categories
Questions about PR And Commit Writing
What does PR And Commit Writing do?
Write commit messages, PR titles/descriptions, and GitHub comments with a user-first style; apply release-drafter-compatible labels; produce release-note-ready PR titles. PR And Commit Writing is an agent skill from PSBrew/MkPFS. Write commit messages, PR titles/descriptions, and GitHub comments with a user-first style; apply release-drafter-compatible labels; produce release-note-ready PR titles.
When should I use PR And Commit Writing?
PR And Commit Writing fits situations like: tasks that involve Commit messages; tasks that involve Changelog and release notes.
How do I install PR And Commit Writing in Claude Code?
Run `npx skills add PSBrew/MkPFS --skill pr-and-commit-writing -a claude-code`. Or copy the skill folder (.claude/skills/pr-and-commit-writing in PSBrew/MkPFS) into .claude/skills/pr-and-commit-writing in your project. Claude Code loads it when a task matches its description.
How do I install PR And Commit Writing in Codex?
Run `npx skills add PSBrew/MkPFS --skill pr-and-commit-writing -a codex`. Or copy the skill folder (.claude/skills/pr-and-commit-writing in PSBrew/MkPFS) into .agents/skills/pr-and-commit-writing in your project. Codex loads it when a task matches its description.
Can I use PR And Commit Writing 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 PSBrew/MkPFS --skill pr-and-commit-writing -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-and-commit-writing, .gemini/skills/pr-and-commit-writing, .github/skills/pr-and-commit-writing and .opencode/skills/pr-and-commit-writing in your project.
What does PR And Commit Writing need to run?
Going by SKILL.md and its folder, PR And Commit Writing needs the command-line tools its instructions call (gh and make).
Does PR And Commit Writing access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is PR And Commit Writing 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 And Commit Writing use?
PR And Commit Writing is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does PR And Commit Writing use?
About 910 tokens (SKILL.md is roughly 3.6k 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 And Commit Writing?
Skills that share tags, products or a category with PR And Commit Writing: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Plane Release Notes Generator (makeplane/plane, 61k stars), Chinese Commit Conventions (jnMetaCode/superpowers-zh, 8.3k stars) and Release Minor (knuckleswtf/scribe, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PR And Commit Writing?
PSBrew (a GitHub organization) maintains it in PSBrew/MkPFS, which has 174 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 3, 2026.
Source: PSBrew/MkPFS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.