How do I install the Create Pr Commit skill?

Run npx skillmds@latest add tomevault-io/create-pr-commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Create Pr Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Pr Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Pr Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Create Pr Commit?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Pr Commit by tomevault-io — Agent Skill

Name: Create Pr Commit
Author: tomevault-io

Create Pr Commit

Generate branch names, conventional commit messages, and PR titles from real project conventions. Use when asked to propose commit/PR text (especially /create-commit or /create-pr) while validating types/scopes against repo standards. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Create Commit / PR / Branch Names

Overview

Produce high-signal Git metadata that matches the repository's actual conventions instead of inventing random types or scopes.

Workflow

Classify the change intent
- Determine the primary change type: feat, fix, docs, style, refactor, perf, test, build, ci, chore, or revert.
- If multiple apply, choose the dominant user-facing impact.
Discover project conventions before proposing text
- Inspect repo convention sources in this order:
  1. .github/ (PR templates, issue forms, workflows, actions, labels, release config)
  2. CONTRIBUTING*, README*, commit lint config (commitlint.*, package.json, .cz*, .commitlintrc*)
  3. Existing git history (if available) for recurring scopes/types
- Extract:
  - allowed commit types (if restricted)
  - known scopes (directory or domain names)
  - branch naming pattern (if documented)
  - title casing rules for PRs/commits
Pick a scope using evidence
- Prefer scopes explicitly documented by the repo.
- If none are documented, derive from affected area (e.g., api, ui, docs, ci).
- Never fabricate an arbitrary scope when confidence is low.
- If a new scope is reasonable, output: suggest new scope: <scope> with one short reason.
Generate branch name options
- Output 1-3 options using detected pattern. If unknown, default to:
  - <type>/<short-kebab-title>
  - <type>/<scope>-<short-kebab-title> (only when scope is validated)
Generate commit title options
- Output 1-3 options using:
  - type(scope): title
  - or type: title when scope is omitted.
- Use lowercase English, imperative mood, no trailing period.
- Keep under ~72 characters when possible.
Generate PR title options
- Output 1-3 options aligned with repository style.
- If no explicit PR style exists, mirror commit title semantics but allow natural readability.
Return a compact rationale block
- Include:
  - type chosen
  - scope source (or no reliable scope found)
  - branch pattern source (or fallback used)

Output Template

branch names:
- ...
- ...

commit titles:
- ...
- ...

pr titles:
- ...
- ...

notes:
- type chosen: ...
- scope source: ...
- branch pattern source: ...
- suggest new scope: ... (optional)

Heuristics

Prefer clarity over cleverness.
Omit scope when uncertain.
Keep semantic consistency across branch, commit, and PR titles.
Avoid over-specific scopes tied to one file unless repo conventions do so.

Examples

Branch: docs/update-contributing-guidelines
Commit: docs: update contributing guidelines
PR: docs: update contributing guidelines
Branch: feat/auth-add-oauth-callback
Commit: feat(auth): add oauth callback handler
PR: feat(auth): add oauth callback handler
Notes: suggest new scope: auth-flow (repo has auth and billing, but no flow-level scope yet)

Source: HugoRCD/hr-folio — distributed by TomeVault.

---name: create-pr-commitdescription: Generate branch names, conventional commit messages, and PR titles from real project conventions. Use when asked to propose commit/PR text (especially /create-commit or /create-pr) while validating types/scopes against repo standards. Use when this capability is needed.---# Create Commit / PR / Branch Names## OverviewProduce high-signal Git metadata that matches the repository's **actual** conventions instead of inventing random types or scopes.## Workflow1. **Classify the change intent** - Determine the primary change type: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, or `revert`. - If multiple apply, choose the dominant user-facing impact.2. **Discover project conventions before proposing text** - Inspect repo convention sources in this order: 1. `.github/` (PR templates, issue forms, workflows, actions, labels, release config) 2. `CONTRIBUTING*`, `README*`, commit lint config (`commitlint.*`, `package.json`, `.cz*`, `.commitlintrc*`) 3. Existing git history (if available) for recurring scopes/types - Extract: - allowed commit types (if restricted) - known scopes (directory or domain names) - branch naming pattern (if documented) - title casing rules for PRs/commits3. **Pick a scope using evidence** - Prefer scopes explicitly documented by the repo. - If none are documented, derive from affected area (e.g., `api`, `ui`, `docs`, `ci`). - **Never fabricate an arbitrary scope** when confidence is low. - If a new scope is reasonable, output: `suggest new scope: <scope>` with one short reason.4. **Generate branch name options** - Output 1-3 options using detected pattern. If unknown, default to: - `<type>/<short-kebab-title>` - `<type>/<scope>-<short-kebab-title>` (only when scope is validated)5. **Generate commit title options** - Output 1-3 options using: - `type(scope): title` - or `type: title` when scope is omitted. - Use lowercase English, imperative mood, no trailing period. - Keep under ~72 characters when possible.6. **Generate PR title options** - Output 1-3 options aligned with repository style. - If no explicit PR style exists, mirror commit title semantics but allow natural readability.7. **Return a compact rationale block** - Include: - `type chosen` - `scope source` (or `no reliable scope found`) - `branch pattern source` (or fallback used)## Output Template```textbranch names:- ...- ...commit titles:- ...- ...pr titles:- ...- ...notes:- type chosen: ...- scope source: ...- branch pattern source: ...- suggest new scope: ... (optional)```## Heuristics- Prefer clarity over cleverness.- Omit scope when uncertain.- Keep semantic consistency across branch, commit, and PR titles.- Avoid over-specific scopes tied to one file unless repo conventions do so.## Examples- Branch: `docs/update-contributing-guidelines`- Commit: `docs: update contributing guidelines`- PR: `docs: update contributing guidelines`- Branch: `feat/auth-add-oauth-callback`- Commit: `feat(auth): add oauth callback handler`- PR: `feat(auth): add oauth callback handler`- Notes: `suggest new scope: auth-flow (repo has auth and billing, but no flow-level scope yet)`---> Source: [HugoRCD/hr-folio](https://github.com/HugoRCD/hr-folio) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions