ruby-style-guide
Ruby code style conventions. Use when writing, reviewing, or refactoring Ruby code.
Installation
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
Voir la source ↗GuidesInstructions
Ruby Style Guide
Apply these conventions when writing or modifying Ruby code.
Guidelines
- When writing a Ruby script or CLI, always use Thor.
- Prefer double quotes for strings; use single quotes only when the string contains double quotes, in shell commands with interpolation, or when following existing code patterns.
- Use parallel assignment for instance variables when initializing from local variables with matching names; split across two lines when assigning 3 or more.
- Indent private methods by 2 additional spaces after the
privatekeyword. - Prefer
case whenoverif elsiffor multiple conditional branches. - Put
ifandunlesson a separate line, except when usingreturnorraisewithout arguments or with one short argument:return if failed?,return false if failed?,raise unless succeeded?,raise error unless succeeded? - Use guard clauses for early returns.
- Use safe navigation operator (
&.) for nil checks. - Add a blank line after multi-line block headers before the block body.
- Use multi-line, leading-dot chaining when calling more than one method in a row.
- Prefer chaining over temporary variables when it stays readable;
thenandtapare often helpful. - Prefer numbered parameters (
_1,_2) for small blocks; useitonly when numbered params don't work. - Prefer endless method definitions for simple, single-expression methods.
Exemples
Consultez les exemples du dépôt source.
Voir la source ↗Historique source
- Date d’indexation
- 2026-01-20
- Mise à jour de l’index
- 2026-01-26
- Branch
- main
Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!