What is the 'One Sentence' test?

If you cannot describe the purpose of a Pull Request in a single sentence without using the word 'and', the task is too large and must be split.

How does this skill handle bug fixes found during feature work?

It mandates branching from main for a separate bug fix PR to be merged independently, rather than bundling the fix with a new feature.

Why separate styling from functional changes?

Separating CSS from logic reduces review complexity and prevents visual changes from obscuring functional logic bugs or regression risks.

What is the recommended file count per PR?

This skill targets 2-5 files per PR, with a maximum of 7-8 files, to ensure every change is focused and easy for team members to audit.

Vanilla Rails Work Breakdown

Name: Vanilla Rails Work Breakdown
Author: ZempTime

byZempTime

•

Productivity & Workflow

Enforces atomic pull request discipline by breaking down Rails feature development into single-sentence, small-scope tasks.

About

This skill guides Claude to follow a strict 'Vanilla Rails' workflow for breaking down complex features into manageable, reviewable pull requests. It enforces a 'one sentence per PR' rule, prohibits the use of 'and' in task descriptions, and mandates the separation of concerns like styling, bug fixes, and refactoring into their own independent units of work. By targeting 2-5 files per PR, it ensures high-quality code reviews and faster shipping cycles consistent with the 37signals development philosophy.

Key Features

Validates task scope using the 'One Sentence' test with no 'and' allowed.
1 GitHub stars
Bundles related Rails components like Migrations + Models or Controllers + Views correctly.
Enforces a strict 2-5 file limit per Pull Request for easier reviews.
Automatically separates styling, bug fixes, and refactoring from feature work.
Standardizes commit messages with present-tense, prefix-free formatting.

Use Cases

Refactoring legacy codebases without mixing logic changes and visual updates.
Planning a complex Rails feature while maintaining small, reviewable PRs.
Implementing a 37signals-inspired 'Vanilla Rails' development workflow for teams.

About

Key Features

Validates task scope using the 'One Sentence' test with no 'and' allowed.
1 GitHub stars
Bundles related Rails components like Migrations + Models or Controllers + Views correctly.
Enforces a strict 2-5 file limit per Pull Request for easier reviews.
Automatically separates styling, bug fixes, and refactoring from feature work.
Standardizes commit messages with present-tense, prefix-free formatting.

Use Cases

Refactoring legacy codebases without mixing logic changes and visual updates.
Planning a complex Rails feature while maintaining small, reviewable PRs.
Implementing a 37signals-inspired 'Vanilla Rails' development workflow for teams.