OpenParable
Skip to content
← Back to skills

Reaparr Git Commit

Development
reaparr-git-commit

Reaparr Git Commit is an Agent Skill for development published in the Reaparr/Reaparr repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when preparing or creating git commits in Reaparr, including commit message formatting, scope selection, and branch targeting rules.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Reaparr/Reaparr/blob/HEAD/.skillshare/skills/reaparr-git-commit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/reaparr-git-commit, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Reaparr Git Commit

Purpose

This skill defines Reaparr commit and branching conventions. Use it whenever creating commit messages, reviewing commit messages, or validating branch targeting before opening a PR.

Commit Message Format

Use this exact pattern:

<type>(<scope>): <Imperative message>

Commit Message Rules

FieldRules
Typefeat, fix, refactor, perf, test, docs, build, chore, style
ScopeWebAPI for backend, Web-UI for frontend
MessageImperative present tense, capitalize first word, no trailing punctuation

Scope Selection Rule

  • All frontend-related changes use scope Web-UI.
  • All other changes use scope WebAPI.

AI Attribution Rule

Never add AI attribution trailers.

Do not include trailers such as:

Co-Authored-By: Claude ...

Branching Rules

  • dev is the integration branch and PR target.
  • Feature branches merge into dev.

Quick Examples

Good:

feat(WebAPI): Add Library sync endpoint
fix(Web-UI): Correct download status badge
test(WebAPI): Add handler validation tests

Bad:

feat(webapi): added endpoint.
fix: download status bug
refactor(Web-UI): Refactor component

Why bad:

  • Wrong scope casing (webapi instead of WebAPI)
  • Message not imperative or not capitalized correctly
  • Trailing punctuation
  • Missing scope

Common Mistakes

  • Using a scope other than WebAPI or Web-UI
  • Writing past-tense or lowercase commit messages
  • Adding trailing punctuation
  • Omitting the scope
  • Adding AI attribution trailers
  • Targeting a PR branch other than dev