project-github-titles

Standardize GitHub commit and PR titles for the rara repository.

15|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/linkerdog/rara --skill project-github-titles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-github-titles
Source: https://github.com/linkerdog/rara/tree/main/.agents/skills/project-github-titles
Command: npx skills add https://github.com/linkerdog/rara --skill project-github-titles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents malformed or inconsistent commit messages and pull request titles by enforcing RARA’s approved short conventional-title format.

Core Features & Use Cases

  • Conventional subset enforcement: Restricts the title type to feat, fix, chore, or test and disallows unlisted types like docs/refactor/style by mapping guidance to allowed alternatives.
  • Scope and subject formatting rules: Ensures correct structure (type: subject or type(scope): subject), keeps scope short and lower-case, and avoids trailing punctuation like a period.
  • PR body template guidance: Produces PR descriptions in markdown with a clear summary, motivation, optional issue reference, and an acceptable testing line for documentation-only changes.

Use case: When preparing a PR for a UI workflow improvement, generate a title like fix(tui): keep approval overlay above transcript and follow it with a compliant PR body that clearly states motivation and validation.

Quick Start

Tell the agent to generate a GitHub commit title and PR title for the following change, following the RARA project-github-titles rules and using only the allowed types and formatting.

Frequently Asked Questions about project-github-titles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I format conventional commit messages and pull request titles correctly?

Conventional commit messages and PR titles require the format type: subject or type(scope): subject. The type must be feat, fix, chore, or test, with a short lowercase scope and no trailing punctuation in the subject line.

What types are allowed for conventional commit titles?

Allowed conventional commit types are restricted to feat, fix, chore, and test. Unlisted types like docs, refactor, or style are disallowed and must be mapped to permitted alternatives for compliant title formatting.

How do I write a PR body for documentation-only changes?

PR bodies for documentation-only changes should use markdown containing a clear summary, motivation, optional issue reference, and an acceptable testing line stating validation was performed via documentation review.

Does this commit title formatter support types like docs or refactor?

No, commit types like docs and refactor are not supported. The formatter enforces a restricted subset of feat, fix, chore, and test, mapping disallowed types to approved alternatives to maintain project standards.

Why do my pull request titles fail repository checks?

Pull request titles fail repository checks when they use unallowed types, missing scopes, or trailing periods. Enforcing the type(scope): subject grammar with lowercase scopes and restricted types resolves validation errors.