worker-quality-rails

To enforce atomic commits and prevent WIP commits in Rails, you can use a skill that mandates self-contained units of work and blocks incomplete changes from being committed. This ensures each commit represents a meaningful, explanatory unit.

Managing technical debt during issue execution requires a strict policy mandating immediate fixes for critical and high findings while prohibiting carry-over. This prevents unresolved issues from accumulating across development cycles.

Requiring passing tests and linters before committing code involves enforcing a pre-commit quality invariant that blocks the commit process until all test suites and linting checks pass successfully.

Yes, you can define an output contract for completed Rails tasks by enforcing a strict set of quality invariants that dictate exactly what information and code state must be provided upon task completion.

Yes, this code quality enforcement skill works without additional dependencies, allowing you to enforce commit standards, testing requirements, and technical debt policies directly within your existing Rails environment.

Commit messages should explain the reasoning behind changes because enforcing explanatory messages clarifies the 'why' for future maintainers, reducing technical debt and improving overall code maintainability in Rails projects.