Run any Skill in Manus with one click

create-pr-commit

Stars0

Forks0

UpdatedFebruary 10, 2026 at 12:54

Suggest conventional commit or pull request titles in the format type(scope): title, written in lowercase English. Use when asked to propose commit messages or PR titles, especially for /create-commit or /create-pr requests.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

onmax

onmax/claude-config

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	create-pr-commit
description	Suggest conventional commit or pull request titles in the format type(scope): title, written in lowercase English. Use when asked to propose commit messages or PR titles, especially for /create-commit or /create-pr requests.

Create Commit/PR Titles

Workflow

Identify the change type: feat, fix, docs, style, refactor, perf, test, build, ci, chore, or revert.
Check repo health files (e.g., .github/ or contributing docs) for recommended scopes or naming tips.
Propose a concise scope (optional) that names the affected area (e.g., api, ui, docs, ci, auth).
Write a short, imperative title in lowercase English (no trailing period).
Output 1-3 options that follow type(scope): title or type: title.

Heuristics

Prefer clarity over cleverness.
Keep titles under ~72 characters when possible.
If the scope is unclear, omit it rather than guessing.
When multiple change types apply, pick the primary one.

Examples

docs: update contributing guide
feat(auth): add oauth callback handler
fix(ui): prevent double submit on form

More from this repository

same repository

design-interface

onmax/claude-config

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when designing an API, exploring interface options, comparing module shapes, or "design it twice".

2026-02-100

request-refactor-plan

onmax/claude-config

Conversational refactor planner - interview, scope, plan tiny atomic commits. Use when planning a refactor that needs careful incremental steps.

2026-02-100

write-a-prd

onmax/claude-config

Conversational PRD writer - interview, scope, write, then create Linear/GitHub issue. Use when planning a new feature or product requirement.

2026-02-100

pnpm

onmax/claude-config

Use when managing Node.js dependencies with pnpm - provides workspace setup, catalogs, CLI commands, overrides, and CI configuration

2026-02-100

tsdown

onmax/claude-config

Use when bundling TypeScript libraries - provides tsdown configuration, dual ESM/CJS output, .d.ts generation, and plugin authoring

2026-02-100

vite

onmax/claude-config

Use when setting up Vite projects - provides dev server, HMR, build configuration, library mode, and plugin authoring patterns

2026-02-100

name	create-pr-commit
description	Suggest conventional commit or pull request titles in the format type(scope): title, written in lowercase English. Use when asked to propose commit messages or PR titles, especially for /create-commit or /create-pr requests.

Create Commit/PR Titles

Workflow

Identify the change type: feat, fix, docs, style, refactor, perf, test, build, ci, chore, or revert.
Check repo health files (e.g., .github/ or contributing docs) for recommended scopes or naming tips.
Propose a concise scope (optional) that names the affected area (e.g., api, ui, docs, ci, auth).
Write a short, imperative title in lowercase English (no trailing period).
Output 1-3 options that follow type(scope): title or type: title.

Heuristics

Prefer clarity over cleverness.
Keep titles under ~72 characters when possible.
If the scope is unclear, omit it rather than guessing.
When multiple change types apply, pick the primary one.

Examples

docs: update contributing guide
feat(auth): add oauth callback handler
fix(ui): prevent double submit on form