Awesome Reviewers

Verifying Ruby changes

Files: .rb. Derived from 5 scanned source repositories and 66 review prompts on https://awesomereviewers.com. Page: https://awesomereviewers.com/verify/ruby/

How to use this: run every check under Run on every change. Then, for each section under Add when the change touches that describes your diff, run its checks too. Checks catch what a tool can find; then apply the listed review prompts for what tools miss (fetch each prompt’s raw URL).

Usage is the share of scanned repositories in this language that run the tool. A missing tool means no scanned repository runs one the scanner recognises: fall back to the prompts.

Run on every change

• Formatting — no tool detected in the sample. Catches: Layout drift that buries the real change in the diff.
• Linting — no tool detected in the sample. Catches: Bug-prone patterns, unused code and conventions the formatter does not cover.
• Type checking — no tool detected in the sample. Catches: Wrong types, unhandled null or None, call signatures broken across modules.
• Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.

Review prompts (11 in total, most discussed first):

• Use descriptive identifiers — discourse/discourse, Naming Conventions
• Use descriptive specific names — mastodon/mastodon, Naming Conventions
• Self-documenting identifier names — rails/rails, Naming Conventions
• Extract and organize methods — chef/chef, Code Style
• Consistent descriptive naming patterns — chef/chef, Naming Conventions
• Follow established naming patterns — Homebrew/brew, Naming Conventions
• Extract complex logic — mastodon/mastodon, Code Style
• Prefer simpler expressions — rails/rails, Code Style
• Extract duplicate code — discourse/discourse, Code Style
• Simplify complex code blocks — Homebrew/brew, Code Style
• Follow established naming conventions — facebook/react-native, Naming Conventions

Add when the change touches

Authentication, input handling, secrets, permissions

• Security scanning: codeql (40% of repos). Runs via GitHub Action github/codeql-action/analyze. Docs: https://github.com/github/codeql
• Secret scanning — no tool detected in the sample. Catches: Credentials and tokens committed to the repository.
• Dependency audit — no tool detected in the sample. Catches: Known-vulnerable or disallowed dependencies and licenses.

Review prompts (5 in total, most discussed first):

• verify authorization explicitly — discourse/discourse, Security
• Secure credential management — chef/chef, Security
• Content security policy configuration — rails/rails, Security
• Prevent injection vulnerabilities — Homebrew/brew, Security
• Minimize HTML attack surface — mastodon/mastodon, Security

Public APIs, signatures, error paths, nullability

• Type checking — no tool detected in the sample. Catches: Wrong types, unhandled null or None, call signatures broken across modules.
• Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.
• Property-based tests — no tool detected in the sample. Catches: Edge-case inputs nobody wrote a test for; invariants over generated data.

Review prompts (15 in total, most discussed first):

• Prefer explicit nil handling — Homebrew/brew, Null Handling
• Fail gracefully always — chef/chef, Error Handling
• Standardize API integration patterns — Homebrew/brew, API
• Minimize public API surface — rails/rails, API
• Clear error recovery paths — Homebrew/brew, Error Handling
• early nil validation — mastodon/mastodon, Null Handling
• API parameter design — mastodon/mastodon, API
• Initialize nil-prone variables — rails/rails, Null Handling
• Prefer guard clauses — chef/chef, Null Handling
• API parameter clarity — discourse/discourse, API
• Contextual error messages — rails/rails, Error Handling
• Include contextual error information — discourse/discourse, Error Handling

Service and framework code

• Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.
• Version and platform matrix: ci-matrix (20% of repos). Command seen: analyze (language: 3). Docs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations

Algorithms, parsers, data transforms

• Property-based tests — no tool detected in the sample. Catches: Edge-case inputs nobody wrote a test for; invariants over generated data.
• Fuzzing — no tool detected in the sample. Catches: Crashes, panics and hangs on malformed input, especially in parsers and decoders.
• Mutation testing — no tool detected in the sample. Catches: Tests that keep passing whatever the code does.
• Proofs and specifications — no tool detected in the sample. Catches: Design-level bugs in protocols and algorithms, checked against a specification.

Review prompts (5 in total, most discussed first):

• Optimize collection operations — Homebrew/brew, Algorithms
• Choose semantic algorithms — chef/chef, Algorithms
• Efficient data processing — rails/rails, Algorithms
• optimize collection iterations — mastodon/mastodon, Algorithms
• optimize data structure choices — discourse/discourse, Algorithms

Threads, async code, locks, shared state

• Concurrency model checking — no tool detected in the sample. Catches: Races and orderings that fail only under specific interleavings.
• Undefined-behaviour detection — no tool detected in the sample. Catches: Memory-safety and aliasing violations in unsafe code.
• Property-based tests — no tool detected in the sample. Catches: Edge-case inputs nobody wrote a test for; invariants over generated data.

Network calls, retries, timeouts, protocols

• Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.
• Fuzzing — no tool detected in the sample. Catches: Crashes, panics and hangs on malformed input, especially in parsers and decoders.

Review prompts (3 in total, most discussed first):

• Secure network operations — chef/chef, Networking
• Use ASCII-only URLs — Homebrew/brew, Networking
• Network resource limits — mastodon/mastodon, Networking

UI components and pages

• End-to-end browser tests — no tool detected in the sample. Catches: User flows broken across components, routing and the network.
• Linting — no tool detected in the sample. Catches: Bug-prone patterns, unused code and conventions the formatter does not cover.

Databases, migrations, caching

• Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.
• Version and platform matrix: ci-matrix (20% of repos). Command seen: analyze (language: 3). Docs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations

Review prompts (5 in total, most discussed first):

• Database-specific query optimization — rails/rails, Database
• validate migration data comprehensively — discourse/discourse, Migrations
• Optimize database queries — mastodon/mastodon, Database
• Avoid N+1 queries — discourse/discourse, Database
• migration data dependencies — mastodon/mastodon, Migrations

Hot paths and performance

• No tool-based check applies; rely on the prompts.

Review prompts (5 in total, most discussed first):

• Minimize unnecessary object allocations — rails/rails, Performance Optimization
• Minimize unnecessary operations — Homebrew/brew, Performance Optimization
• Memoize expensive operations — chef/chef, Performance Optimization
• batch similar operations — mastodon/mastodon, Performance Optimization
• Cache expensive operations — discourse/discourse, Performance Optimization

Model, prompt and LLM code

• Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.

Logging, metrics, tracing

• No tool-based check applies; rely on the prompts.

Review prompts (1 in total, most discussed first):

• Include contextual log information — discourse/discourse, Logging

CI workflows and configuration files

• CI workflow linting — no tool detected in the sample. Catches: Broken GitHub Actions syntax, script injection, over-broad token permissions.
• File hygiene — no tool detected in the sample. Catches: Invalid JSON, YAML or TOML, merge markers, trailing whitespace, oversized files.

Review prompts (7 in total, most discussed first):

• centralize configuration management — mastodon/mastodon, Configurations
• Configure at proper scope — rails/rails, Configurations
• Explicit configuration over implicit — chef/chef, Configurations
• Safe setting modifications — discourse/discourse, Configurations
• Structured environment configuration — Homebrew/brew, Configurations
• Correct GitHub Actions annotations — Homebrew/brew, CI/CD
• Environment variable validation — facebook/react-native, Configurations

Dependencies and lockfiles

• Dependency audit — no tool detected in the sample. Catches: Known-vulnerable or disallowed dependencies and licenses.
• Lockfile consistency — no tool detected in the sample. Catches: A lockfile that no longer matches its manifest.
• Version and platform matrix: ci-matrix (20% of repos). Command seen: analyze (language: 3). Docs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations

The tests themselves

• Mutation testing — no tool detected in the sample. Catches: Tests that keep passing whatever the code does.
• Version and platform matrix: ci-matrix (20% of repos). Command seen: analyze (language: 3). Docs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations

Review prompts (5 in total, most discussed first):

• Organize tests for clarity — rails/rails, Testing
• optimize test fixtures — discourse/discourse, Testing
• optimize test organization — mastodon/mastodon, Testing
• Use strict test doubles — chef/chef, Testing
• Structure test fixtures clearly — Homebrew/brew, Testing

Documentation and comments

• Docs build — no tool detected in the sample. Catches: Broken cross-references, links and markup in documentation.
• Spelling — no tool detected in the sample. Catches: Typos in identifiers, comments and docs.

Review prompts (4 in total, most discussed first):

• Document with examples — chef/chef, Documentation
• Write complete API examples — rails/rails, Documentation
• Document non-obvious decisions — Homebrew/brew, Documentation
• Example documentation standards — aws/aws-sdk-js, Documentation

Source repositories

rails/rails, mastodon/mastodon, discourse/discourse, Homebrew/brew, chef/chef

This site is open source. Improve this page.