Agent skill · software engineering · aiskillstore
generating-rbs-inline
Generates RBS-inline type annotations directly in Ruby source files as comments. Triggers when adding inline type signatures, annotating Ruby methods with rbs-inline syntax, or generating type comments without existing inline annotations.
Why this skill is useful
Adds specific commands and structured processes for generating RBS-inline annotations that the AI wouldn't reliably generate on its own.
What it needs
Requires rbs-inline installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
RBS-Inline Generation Skill Generate RBS-inline type annotations as comments directly in Ruby source files. Unlike pure RBS which uses separate .rbs files, rbs-inline embeds type information as structured comments within Ruby code. Instructions When generating RBS-inline annotations, always follow these steps. Copy this checklist and track your progress: Rules You MUST NOT run Ruby code of the project. You MUST NOT use untyped. Infer the proper type instead. You MUST ask the user to provide more details if something is not clear. You MUST prepend any command with bundle exec if the project has Gemfile. You MUST use # @rbs comment syntax for inline annotations. You MUST NOT use regular RBS signatures and .rbs files in the project. 1. Analyze the Ruby Source Always perform this step. Read and understand the Ruby source file: Identify all classes, modules, methods, constants and instance variables. Note inheritance, module inclusion and definitions based on metaprogramming. Note visibility modifiers - public, private, protected. Note type parameters for generic classes. 2. Add RBS-Inline Annotations Always perform this step. 1. First, add the magic comment at the top of the Ruby file to enable rbs-inline processing: 2. Then add type annotations as comments directly in the Ruby source file using rbs-inline syntax: Example - Before: Example - After: Follow RBS-inline syntax conventions strictly See syntax.md for the full RBS-inline syntax guide Pay extra attention to Data and Struct types See data-struct-support.md for Data and Struct handling 3. Eliminate untyped Types in Annotations Always perform this step. Review all annotations and replace untyped with proper types. Use code context, method calls, and tests to infer types. Use untyped only as a last resort when type cannot be determined. 4. Review and Refine Annotations Always perform this step. Verify annotations are correct, coherent, and complete. Remove unnecessary untyped types. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/generating-rbs-inline