Using Rubocop Settings to Standardize String Literals with Double Quotes

[dearblue]

When string interpolation is required, string literals must be "converted" to double quotes.
Ultimately, using double quotes consistently from the start ensures greater overall consistency.

---

I plan to enhance the .check.rb file.

[gemini-code-assist]

Code Review

This pull request updates string literals in .check.rb from single quotes to double quotes, aligning with new RuboCop configuration rules added to .github/linters/.rubocop.yml that enforce double quotes. The review feedback suggests two idiomatic Ruby improvements in .check.rb: simplifying the single-element array inclusion check to a direct equality comparison, and using the safe navigation operator (&.each) instead of .to_a.each to handle potential nil values more cleanly.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Using ["git"].include? tree["protocol"] is less efficient and less readable than a direct equality comparison since the array contains only a single element. Simplifying this to tree["protocol"] == "git" is more idiomatic.

  raise "invalid protocol" unless tree["protocol"] == "git" # TODO

[gemini-code-assist]

Using .to_a.each to handle a potential nil value is less idiomatic in modern Ruby. Using the safe navigation operator &.each is cleaner and avoids creating an unnecessary empty array when tree["dependencies"] is nil.

  tree["dependencies"]&.each do |x|