Menu
Ensures issue titles conform with a specific style. Use when creating or editing an issue.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| description | Ensures issue titles conform with a specific style. Use when creating or editing an issue. |
| name | conform-issue-title |
Issue titles use all-lowercase, except for acronyms and proper terms (e.g.
API, JSON, macOS, type names, code identifiers). Only surround type names
and code identifiers with backticks. Examples:
- add a reusable raytracing API
- cash balances as position entities
- merge `Shares` into `Position` and composite `PositionIndex` key
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 PR (Pull Request) titles conform with a specific style. Use when creating or editing a PR.