// Use when preparing or creating git commits in Reaparr, including commit message formatting, scope selection, and branch targeting rules.
Use when doing any Reaparr backend work under src excluding ClientApp, backend tests, backend configs, C# code, FastEndpoints, EF Core, Quartz jobs, SignalR, command handlers, unit tests, integration tests, backend architecture, or backend reviews. This skill must always load before any narrower backend skill.
Use when creating, updating, debugging, or stabilizing Reaparr backend integration tests under tests/IntegrationTests, especially when failures involve async jobs, seeded data, fake Plex responses, filesystem behavior, or end-to-end API and database state validation.
Use when creating or updating C# backend unit tests in Reaparr, especially for handlers, services, endpoints, and jobs that must follow the project's TUnit, Shouldly, Moq, BaseUnitTest, naming, placement, and deterministic test-data conventions.
Use when creating, debugging, or stabilizing Reaparr frontend Cypress integration tests, especially for flaky CI failures, uncaught app exceptions, route/port issues, and deterministic test hardening under src/AppHost/ClientApp/cypress.
Use when creating or updating Vitest unit tests for the Reaparr frontend (Nuxt/Vue/Pinia/RxJS stores), especially for store setup, actions, getters, and RxJS observable flows that must follow the project's boilerplate, path alias, mock data, and naming conventions.
Use when doing any Reaparr frontend work under src/AppHost/ClientApp, including Vue, Nuxt, TypeScript, Pinia, RxJS, Quasar, PrimeVue, Cypress, Vitest, frontend config, frontend reviews, debugging, refactors, and frontend test work. This skill must always load before any narrower frontend skill.
| name | reaparr-git-commit |
| description | Use when preparing or creating git commits in Reaparr, including commit message formatting, scope selection, and branch targeting rules. |
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.
Use this exact pattern:
<type>(<scope>): <Imperative message>
| Field | Rules |
|---|---|
| Type | feat, fix, refactor, perf, test, docs, build, chore, style |
| Scope | WebAPI for backend, Web-UI for frontend |
| Message | Imperative present tense, capitalize first word, no trailing punctuation |
Web-UI.WebAPI.Never add AI attribution trailers.
Do not include trailers such as:
Co-Authored-By: Claude ...
dev is the integration branch and PR target.dev.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:
webapi instead of WebAPI)WebAPI or Web-UIdev