Semi Automatic Code Review
summary
A semi‑automatic review pipeline analyzes Rails code, flags style and correctness issues and suggests concrete fixes: the rails best practice gem scans ASTs (via Ripper) to recommend use scope access, model associations, and replacing manual nil checks with try; an online service at rb.com hooks GitHub pushes, runs checks, stores history, and shows which commit introduced each warning. Teams run it in Guard or Jenkins, write small plugins to codify team rules, and use the tool to remove many unused methods and clean a large legacy codebase.
AI-written summary · about
chapters (10)
- 0:00Semi-automatic code review intro
- 4:06Manual review limitations
- 5:12Code review parts explained
- 6:16Rails Best Practice gem
- 9:30Refactoring technical debt
- 10:36railsbp.com for teams
- 14:41Tool configuration
- 15:46Extending with plugins
- 18:58Open source demo
- 25:27Q&A
related talks
29mCode review, do you speak it?
43mCode Review Tools
23mKeeping Code Style Sanity in a 13-year-old Codebase
24mKeeping Code Style Sanity in a 13-year-old Codebase
01h 02mEffective Code Review
41mCracking the Code Review from Guesswork to Automated Guidance
23mEmbracing Code Quality with Rubocop
53mCode Review Beyond Code Style