Menú
Ensures PR (Pull Request) titles conform with a specific style. Use when creating or editing a PR.
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
Ensures markdown files conform to rumdl linting rules and personal formatting preferences. Use when creating or editing .md files, or when user mentions formatting, linting, or rumdl.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Reference for writing and editing skills well - the vocabulary and principles that make a skill predictable.
Implement a piece of work based on a PRD or set of issues.
Ensures issue titles conform with a specific style. Use when creating or editing an issue.
| description | Ensures PR (Pull Request) titles conform with a specific style. Use when creating or editing a PR. |
| name | conform-pr-title |
The PR title becomes the merge commit message on the main branch.
PR titles follow the "Conventional Commits" format:
<type>[scope]: <description>.
Refer to the /conventional-commits skill as well.
