Menú
Use when preparing commit messages, pull request titles, or first-line summaries for the RARA repository. Enforces the repo's short conventional title subset using feat, fix, chore, or test.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when you need to understand the RARA codebase structure — what each file does, where subsystems live, and how they connect. The index maps every source file to its role.
Use when preparing, validating, tagging, or troubleshooting a RARA release. Enforces the release order that prevents tag versions from diverging from the Cargo package version.
Handle unused code warnings by investigating purpose via journals, then choose the right fix: suppress, wire-up, or remove.
Add or update tests for the RARA codebase. Use when implementing non-trivial behavior changes, fixing regressions, tightening TUI rendering, or adding repo-specific test coverage in Rust. Especially relevant for focused unit tests, TUI snapshot tests, agent/runtime regressions, and behavior-driven test updates in this repository.
Use when creating, updating, or reviewing RARA implementation journals under docs/journal/. Applies to dated rollout notes, implementation checkpoints, validation evidence, and deciding what belongs in a journal versus a feature spec or docs/todo.md.
Use when creating, revising, or reviewing RARA canonical feature specs under docs/features/. Applies to stable runtime, TUI, protocol, memory, provider, skill, plugin, and tool contracts, including scope boundaries and validation matrices.
| name | project-github-titles |
| description | Use when preparing commit messages, pull request titles, or first-line summaries for the RARA repository. Enforces the repo's short conventional title subset using feat, fix, chore, or test. |
Use this skill when writing commit titles, pull request titles, or the first summary line in PR/commentary text for this repository.
Use one of:
type: subjecttype(scope): subjectNever prefix titles with [codex].
Keep title text in English, concise, and specific. Do not end the subject with a period.
RARA intentionally uses a small subset:
feat: user-visible feature or capabilityfix: bug fix or behavior correctionchore: maintenance, dependency, tooling, docs, or non-user-facing cleanuptest: test-only changesDo not use unlisted types such as docs, refactor, or style. Map those to
the closest allowed type, usually chore for docs or maintenance.
Do not use ! breaking-change markers in titles. Describe compatibility impact
in the PR body instead.
Use a scope only when it clarifies the primary touched area. Keep it short and lower-case.
Useful scopes in this repository include:
agenttuitoolsmemorycontextproviderpluginsskillsacpwireciPrefer stable product or domain scopes over file names.
update stuff or misc cleanup.Good examples:
fix(tui): keep approval overlay above transcriptfeat(memory): add local embedding prototypechore(skills): add RARA journal writing skilltest(agent): cover duplicate tool call warningPR descriptions should use markdown and include:
For documentation-only changes, Testing: Not run; documentation-only change.
is acceptable.