generating-sorbet

To generate Sorbet RBI signatures for a Ruby project, you run this skill to analyze Ruby source files and automatically write the corresponding type signatures into the ./rbi directory using strict sig { } blocks.

The best way to add static type checking to legacy Ruby code without modifying source files is to generate standalone RBI signatures in a separate rbi directory, keeping type definitions maintained alongside the original codebase.

Yes, you can update existing RBI files to reflect changes in your Ruby codebase by running this skill, which refreshes the static type signatures to match your current Ruby sources.

Yes, this RBI generation approach works for Ruby gems and generated code, applying strict RBI conventions to maintain type signatures separately in the rbi directory for multi-file projects.

Generated Sorbet signatures need to be placed under the rbi directory to enforce strict RBI conventions, ensuring that static type checking can safely validate Ruby code without altering the actual source files.

A limitation of generating RBI files separately is that you must continuously refresh the standalone signatures to accurately track and reflect any structural changes made to the original Ruby source files.