docscribe 1.1.0 → 1.2.1

data/README.md

@@ -13,26 +13,63 @@ returns), and respects Ruby visibility semantics — without using YARD to parse
 
 - No AST reprinting. Your original code, formatting, and constructs (like `class << self`, `heredocs`, `%i[]`) are
   preserved.
-- Inline-first. Comments are inserted at the start of each `def`/`defs` line.
+- Inline-first. Comments are inserted before method headers without reprinting the AST. For methods with a leading
+  Sorbet `sig`, new docs are inserted above the first `sig`.
 - Heuristic type inference for params and return values, including conditional returns in rescue branches.
-- Optional rewrite mode for regenerating existing method docs.
+- Safe and aggressive update modes:
+    - safe mode inserts missing docs, merges existing doc-like blocks, and normalizes sortable tags;
+    - aggressive mode rebuilds existing doc blocks.
 - Ruby 3.4+ syntax supported using Prism translation (see "Parser backend" below).
+- Optional external type integrations:
+    - RBS via `--rbs` / `--sig-dir`;
+    - Sorbet via inline `sig` declarations and RBI files with `--sorbet` / `--rbi-dir`.
+- Optional `@!attribute` generation for:
+    - `attr_reader` / `attr_writer` / `attr_accessor`;
+    - `Struct.new` declarations in both constant-assigned and class-based styles.
 
-Why not YARD? We started with YARD's parser, but switched to an AST-based in-place rewriter for maximum preservation of
-source structure and exact control over Ruby semantics.
+Common workflows:
+
+- Inspect what safe doc updates would be applied: `docscribe lib`
+- Apply safe doc updates: `docscribe -a lib`
+- Apply aggressive doc updates: `docscribe -A lib`
+- Use RBS signatures when available: `docscribe -a --rbs --sig-dir sig lib`
+- Use Sorbet signatures when available: `docscribe -a --sorbet --rbi-dir sorbet/rbi lib`
+
+## Contents
 
 * [Docscribe](#docscribe)
+    * [Contents](#contents)
     * [Installation](#installation)
     * [Quick start](#quick-start)
     * [CLI](#cli)
-    * [Inline behavior](#inline-behavior)
-        * [Rewrite mode](#rewrite-mode)
+        * [Options](#options)
+        * [Examples](#examples)
+    * [Update strategies](#update-strategies)
+        * [Safe strategy](#safe-strategy)
+        * [Aggressive strategy](#aggressive-strategy)
+        * [Output markers](#output-markers)
+    * [Parser backend (Parser gem vs Prism)](#parser-backend-parser-gem-vs-prism)
+    * [External type integrations (optional)](#external-type-integrations-optional)
+        * [RBS](#rbs)
+        * [Sorbet](#sorbet)
+        * [Inline Sorbet example](#inline-sorbet-example)
+        * [Sorbet RBI example](#sorbet-rbi-example)
+        * [Sorbet comment placement](#sorbet-comment-placement)
+        * [Generic type formatting](#generic-type-formatting)
+        * [Notes and fallback behavior](#notes-and-fallback-behavior)
     * [Type inference](#type-inference)
     * [Rescue-aware returns and @raise](#rescue-aware-returns-and-raise)
     * [Visibility semantics](#visibility-semantics)
     * [API (library) usage](#api-library-usage)
     * [Configuration](#configuration)
-        * [CLI](#cli-1)
+        * [Filtering](#filtering)
+        * [`attr_*` example](#attr_-example)
+        * [`Struct.new` examples](#structnew-examples)
+            * [Constant-assigned struct](#constant-assigned-struct)
+            * [Class-based struct](#class-based-struct)
+        * [Merge behavior](#merge-behavior)
+        * [Param tag style](#param-tag-style)
+        * [Create a starter config](#create-a-starter-config)
     * [CI integration](#ci-integration)
     * [Comparison to YARD's parser](#comparison-to-yards-parser)
     * [Limitations](#limitations)
@@ -45,7 +82,7 @@ source structure and exact control over Ruby semantics.
 Add to your Gemfile:
 
 ```ruby
-gem 'docscribe'
+gem "docscribe"
 ```
 
 Then:
@@ -100,7 +137,6 @@ echo "...code above..." | docscribe --stdin
 Output:
 
 ```ruby
-
 class Demo
   # +Demo#foo+ -> Integer
   #
@@ -148,11 +184,11 @@ class Demo
 end
 ```
 
-Notes:
-
-- The tool inserts doc headers at the start of def/defs lines and preserves everything else.
-- Class methods show with a dot (`+Demo.bump+`, `+Demo.internal+`).
-- Methods inside `class << self` under private are marked `@private.`
+> [!NOTE]
+> - The tool inserts doc headers before method headers and preserves everything else.
+> - For methods with a leading Sorbet `sig`, docs are inserted above the first `sig`.
+> - Class methods show with a dot (`+Demo.bump+`, `+Demo.internal+`).
+> - Methods inside `class << self` under `private` are marked `@private`.
 
 ## CLI
 
@@ -160,174 +196,458 @@ Notes:
 docscribe [options] [files...]
 ```
 
-Options:
+Docscribe has three main ways to run:
+
+- **Inspect mode** (default): checks what safe doc updates would be applied and exits non-zero if files need changes.
+- **Safe autocorrect** (`-a`, `--autocorrect`): writes safe, non-destructive updates in place.
+- **Aggressive autocorrect** (`-A`, `--autocorrect-all`): rewrites existing doc blocks more aggressively.
+- **STDIN mode** (`--stdin`): reads Ruby source from STDIN and prints rewritten source to STDOUT.
+
+If you pass no files and don’t use `--stdin`, Docscribe processes the current directory recursively.
+
+### Options
+
+- `-a`, `--autocorrect`  
+  Apply safe doc updates in place.
+
+- `-A`, `--autocorrect-all`  
+  Apply aggressive doc updates in place.
+
+- `--stdin`  
+  Read source from STDIN and print rewritten output.
+
+- `--verbose`  
+  Print per-file actions.
+
+- `--explain`  
+  Show detailed reasons for each file that would change.
+
+- `--rbs`  
+  Use RBS signatures for `@param`/`@return` when available (falls back to inference).
+
+- `--sig-dir DIR`  
+  Add an RBS signature directory (repeatable). Implies `--rbs`.
+
+- `--include PATTERN`  
+  Include PATTERN (method id or file path; glob or `/regex/`).
+
+- `--exclude PATTERN`  
+  Exclude PATTERN (method id or file path; glob or `/regex/`). Exclude wins.
+
+- `--include-file PATTERN`  
+  Only process files matching PATTERN (glob or `/regex/`).
+
+- `--exclude-file PATTERN`  
+  Skip files matching PATTERN (glob or `/regex/`). Exclude wins.
+
+- `-C`, `--config PATH`  
+  Path to config YAML (default: `docscribe.yml`).
 
-- `--stdin` Read source from STDIN and print with docs inserted.
-- `--write` Rewrite files in place (inline mode).
-- `--check` Dry-run: exit 1 if any file would change (useful in CI).
-- `--rewrite` Replace any existing comment block above methods (see “Rewrite mode” below).
-- `--version` Print version and exit.
-- `-h`, `--help` Show help.
+- `-v`, `--version`  
+  Print version and exit.
 
-Examples:
+- `-h`, `--help`  
+  Show help.
 
-- Print to stdout for one file:
+### Examples
+
+- Inspect a directory:
   ```shell
-  docscribe path/to/file.rb
+  docscribe lib
   ```
-- Rewrite files in place (ensure a clean working tree):
+
+- Apply safe updates:
+  ```shell
+  docscribe -a lib
+  ```
+
+- Apply aggressive updates:
   ```shell
-  docscribe --write lib/**/*.rb
+  docscribe -A lib
   ```
-- CI check (fail if docs are missing/stale):
+
+- Preview output for a single file via STDIN:
   ```shell
-  docscribe --check lib/**/*.rb
+  cat path/to/file.rb | docscribe --stdin
   ```
-- Rewrite existing doc blocks above methods (regenerate headers/tags):
+
+- Use RBS signatures:
   ```shell
-  docscribe --rewrite --write lib/**/*.rb
+  docscribe -a --rbs --sig-dir sig lib
   ```
-- Check a directory (Docscribe expands directories to `**/*.rb`):
-  ```bash
-  docscribe --check lib
+
+- Show detailed reasons for files that would change:
+  ```shell
+  docscribe --verbose --explain lib
   ```
 
-## Inline behavior
+## Update strategies
+
+Docscribe supports two update strategies: **safe** and **aggressive**.
+
+### Safe strategy
+
+Used by:
+
+- default inspect mode: `docscribe lib`
+- safe write mode: `docscribe -a lib`
+
+Safe strategy:
+
+- inserts docs for undocumented methods
+- merges missing tags into existing **doc-like** blocks
+- normalizes configurable tag order inside sortable tag runs
+- preserves existing prose and comments where possible
+
+This is the recommended day-to-day mode.
+
+### Aggressive strategy
+
+Used by:
+
+- aggressive write mode: `docscribe -A lib`
 
-- Inserts comment blocks immediately above def/defs nodes.
-- Skips methods that already have a comment directly above them (does not merge into existing comments) unless you pass
-  `--rewrite`.
-- Maintains original formatting and constructs; only adds comments.
+Aggressive strategy:
 
-### Rewrite mode
+- rebuilds existing doc blocks
+- replaces existing generated documentation more fully
+- is more invasive than safe mode
 
-- With `--rewrite`, Docscribe will remove the contiguous comment block immediately above a method (plus intervening
-  blank
-  lines) and replace it with a fresh generated block.
-- This is useful to refresh docs across a codebase after improving inference or rules.
-- Use with caution (prefer a clean working tree and review diffs).
+Use it when you want to rebaseline or regenerate docs wholesale.
 
-### Output markers in CI
+### Output markers
 
-When using `--check`, Docscribe prints one character per file:
+In inspect mode, Docscribe prints one character per file:
 
-- `.` = file is up-to-date
-- `F` = file would change (missing/stale docs)
+- `.` = file is up to date
+- `F` = file would change
+- `E` = file had an error
 
-When using `--write`:
+In write modes:
 
 - `.` = file already OK
-- `C` = file was corrected and rewritten
+- `C` = file was updated
+- `E` = file had an error
 
-Docscribe prints a summary at the end and exits non-zero in `--check` mode if any file would change.
+With `--verbose`, Docscribe prints per-file statuses instead.
+
+With `--explain`, Docscribe also prints detailed reasons, such as:
+
+- missing `@param`
+- missing `@return`
+- missing module_function note
+- unsorted tags
 
 ## Parser backend (Parser gem vs Prism)
 
 Docscribe internally works with `parser`-gem-compatible AST nodes and `Parser::Source::*` objects (so it can use
-`Parser::Source::TreeRewriter` without changing your formatting).
+`Parser::Source::TreeRewriter` without changing formatting).
 
 - On Ruby **<= 3.3**, Docscribe parses using the `parser` gem.
-- On Ruby **>= 3.4**, Docscribe parses using **Prism** and translates the tree into the `parser` gem’s AST (so tooling
-  stays compatible).
+- On Ruby **>= 3.4**, Docscribe parses using **Prism** and translates the tree into the `parser` gem's AST.
 
 You can force a backend with an environment variable:
 
-```bash
-DOCSCRIBE_PARSER_BACKEND=parser bundle exec docscribe --check lib
-DOCSCRIBE_PARSER_BACKEND=prism  bundle exec docscribe --check lib
+```shell
+DOCSCRIBE_PARSER_BACKEND=parser bundle exec docscribe lib
+DOCSCRIBE_PARSER_BACKEND=prism  bundle exec docscribe lib
 ```
 
-## Type inference
+## External type integrations (optional)
 
-Heuristics (best-effort):
+Docscribe can improve generated `@param` and `@return` types by reading external signatures instead of relying only on
+AST inference.
 
-Parameters:
+> [!IMPORTANT]
+> When external type information is available, Docscribe resolves signatures in this order:
+> - inline Sorbet `sig` declarations in the current Ruby source;
+> - Sorbet RBI files;
+> - RBS files;
+> - AST inference fallback.
+>
+> If an external signature cannot be loaded or parsed, Docscribe falls back to normal inference instead of failing.
 
-- `*args` -> `Array`
-- `**kwargs` -> `Hash`
-- `&block` -> `Proc`
-- keyword args:
-    - verbose: `true` -> `Boolean`
-    - options: `{}` -> `Hash`
-    - kw: (no default) -> `Object`
-- positional defaults:
-    - `42` -> `Integer`, `1.0` -> `Float`, `'x'` -> `String`, `:ok` -> `Symbol`
-    - `[]` -> `Array`, `{}` -> `Hash`, `/x/` -> `Regexp`, `true`/`false` -> `Boolean`, `nil` -> `nil`
+### RBS
 
-Return values:
+Docscribe can read method signatures from `.rbs` files and use them to generate more accurate parameter and return
+types.
 
-- For simple bodies, Docscribe looks at the last expression or explicit return:
-    - `42` -> `Integer`
-    - `:ok` -> `Symbol`
-    - Unions with nil become optional types (e.g., `String` or `nil` -> `String?`).
-- For control flow (`if`/`case`), it unifies branches conservatively.
+CLI:
 
-## Rescue-aware returns and @raise
+```shell
+docscribe -a --rbs --sig-dir sig lib
+```
 
-Docscribe detects exceptions and rescue branches:
+You can pass `--sig-dir` multiple times:
 
-- Rescue exceptions become `@raise` tags:
-    - `rescue Foo, Bar` -> `@raise [Foo]` and `@raise [Bar]`
-    - bare rescue -> `@raise [StandardError]`
-    - (optional) explicit raise/fail also adds a tag (`raise Foo` -> `@raise [Foo]`, `raise` ->
-      `@raise [StandardError]`).
+```shell
+docscribe -a --rbs --sig-dir sig --sig-dir vendor/sigs lib
+```
 
-- Conditional return types for rescue branches:
-    - Docscribe adds `@return [Type]` if `ExceptionA`, `ExceptionB` for each rescue clause.
+Config:
+
+```yaml
+rbs:
+  enabled: true
+  sig_dirs:
+    - sig
+  collapse_generics: false
+```
 
 Example:
 
 ```ruby
+# Ruby source
+class Demo
+  def foo(verbose:, count:)
+    "body says String"
+  end
+end
+```
 
-class X
-  def a
-    42
-  rescue Foo, Bar
-    "fallback"
+```ruby.rbs
+# sig/demo.rbs
+class Demo
+    def foo: (verbose: bool, count: Integer) -> Integer
+end
+```
+
+Generated docs will prefer the RBS signature over inferred Ruby types:
+
+```ruby
+
+class Demo
+  # +Demo#foo+ -> Integer
+  #
+  # Method documentation.
+  #
+  # @param [Boolean] verbose Param documentation.
+  # @param [Integer] count Param documentation.
+  # @return [Integer]
+  def foo(verbose:, count:)
+    'body says String'
   end
+end
+```
+
+### Sorbet
+
+Docscribe can also read Sorbet signatures from:
+
+- inline `sig` declarations in Ruby source
+- RBI files
+
+CLI:
+
+```shell
+docscribe -a --sorbet lib
+```
+
+With RBI directories:
 
-  def b
-    risky
-  rescue
-    "n"
+```shell
+docscribe -a --sorbet --rbi-dir sorbet/rbi lib
+```
+
+You can pass `--rbi-dir` multiple times:
+
+```shell
+docscribe -a --sorbet --rbi-dir sorbet/rbi --rbi-dir rbi lib
+```
+
+Config:
+
+```yaml
+sorbet:
+  enabled: true
+  rbi_dirs:
+    - sorbet/rbi
+    - rbi
+  collapse_generics: false
+```
+
+### Inline Sorbet example
+
+```ruby
+class Demo
+  extend T::Sig
+
+  sig { params(verbose: T::Boolean, count: Integer).returns(Integer) }
+  def foo(verbose:, count:)
+    'body says String'
   end
 end
 ```
 
-Becomes:
+Docscribe will use the Sorbet signature instead of the inferred body type:
 
 ```ruby
+class Demo
+  extend T::Sig
 
-class X
-  # +X#a+ -> Integer
+  # +Demo#foo+ -> Integer
   #
   # Method documentation.
   #
-  # @raise [Foo]
-  # @raise [Bar]
+  # @param [Boolean] verbose Param documentation.
+  # @param [Integer] count Param documentation.
   # @return [Integer]
-  # @return [String] if Foo, Bar
-  def a
-    42
-  rescue Foo, Bar
-    "fallback"
+  sig { params(verbose: T::Boolean, count: Integer).returns(Integer) }
+  def foo(verbose:, count:)
+    'body says String'
+  end
+end
+```
+
+### Sorbet RBI example
+
+```ruby
+# Ruby source
+class Demo
+  def foo(verbose:, count:)
+    'body says String'
   end
+end
+```
+
+```ruby
+# sorbet/rbi/demo.rbi
+class Demo
+  extend T::Sig
+
+  sig { params(verbose: T::Boolean, count: Integer).returns(Integer) }
+  def foo(verbose:, count:); end
+end
+```
+
+With:
+
+```shell
+docscribe -a --sorbet --rbi-dir sorbet/rbi lib
+```
+
+Docscribe will use the RBI signature for generated docs.
+
+### Sorbet comment placement
+
+For methods with a leading Sorbet `sig`, Docscribe treats the signature as part of the method header.
+
+That means:
+
+- new docs are inserted **above the first `sig`**
+- existing docs **above the `sig`** are recognized and merged
+- existing legacy docs **between `sig` and `def`** are also recognized
+
+Example input:
+
+```ruby
+# demo.rb
+class Demo
+  extend T::Sig
+
+  sig { returns(Integer) }
+  def foo
+    1
+  end
+end
+```
+
+Example output:
+
+```ruby
+# demo.rb
+class Demo
+  extend T::Sig
 
-  # +X#b+ -> Object
+  # +Demo#foo+ -> Integer
   #
   # Method documentation.
   #
-  # @raise [StandardError]
-  # @return [Object]
-  # @return [String] if StandardError
-  def b
-    risky
-  rescue
-    "n"
+  # @return [Integer]
+  sig { returns(Integer) }
+  def foo
+    1
   end
 end
 ```
 
+### Generic type formatting
+
+Both RBS and Sorbet integrations support `collapse_generics`.
+
+When disabled:
+
+```yaml
+rbs:
+  collapse_generics: false
+
+sorbet:
+  collapse_generics: false
+```
+
+Docscribe preserves generic container details where possible, for example:
+
+- `Array<String>`
+- `Hash<Symbol, Integer>`
+
+When enabled:
+
+```yaml
+rbs:
+  collapse_generics: true
+
+sorbet:
+  collapse_generics: true
+```
+
+Docscribe simplifies container types to their outer names, for example:
+
+- `Array`
+- `Hash`
+
+### Notes and fallback behavior
+
+- External signature support is the **best effort**.
+- If a signature source cannot be loaded or parsed, Docscribe falls back to AST inference.
+- RBS and Sorbet integrations are used only to improve generated types; Docscribe still rewrites Ruby source directly.
+- Sorbet support does not require changing your documentation style — it only improves generated `@param` and `@return`
+  tags when signatures are available.
+
+## Type inference
+
+Heuristics (best-effort).
+
+Parameters:
+
+- `*args` -> `Array`
+- `**kwargs` -> `Hash`
+- `&block` -> `Proc`
+- keyword args:
+    - `verbose: true` -> `Boolean`
+    - `options: {}` -> `Hash`
+    - `kw:` (no default) -> `Object`
+- positional defaults:
+    - `42` -> `Integer`, `1.0` -> `Float`, `'x'` -> `String`, `:ok` -> `Symbol`
+    - `[]` -> `Array`, `{}` -> `Hash`, `/x/` -> `Regexp`, `true`/`false` -> `Boolean`, `nil` -> `nil`
+
+Return values:
+
+- For simple bodies, Docscribe looks at the last expression or explicit `return`.
+- Unions with `nil` become optional types (e.g. `String` or `nil` -> `String?`).
+- For control flow (`if`/`case`), it unifies branches conservatively.
+
+## Rescue-aware returns and @raise
+
+Docscribe detects exceptions and rescue branches:
+
+- Rescue exceptions become `@raise` tags:
+    - `rescue Foo, Bar` -> `@raise [Foo]` and `@raise [Bar]`
+    - bare rescue -> `@raise [StandardError]`
+    - explicit `raise`/`fail` also adds a tag (`raise Foo` -> `@raise [Foo]`, `raise` -> `@raise [StandardError]`)
+
+- Conditional return types for rescue branches:
+    - Docscribe adds `@return [Type] if ExceptionA, ExceptionB` for each rescue clause
+
 ## Visibility semantics
 
 We match Ruby's behavior:
@@ -342,10 +662,26 @@ Inline tags:
 - `@private` is added for methods that are private in context.
 - `@protected` is added similarly for protected methods.
 
+> [!IMPORTANT]
+> `module_function`: Docscribe documents methods affected by `module_function` as module methods (`M.foo`) rather than
+> instance methods (`M#foo`), because that is usually the callable/public API. If a method was previously private as an
+> instance method, Docscribe will avoid marking the generated docs as `@private` after it is promoted to a module
+> method.
+
+```ruby
+module M
+  private
+
+  def foo; end
+
+  module_function :foo
+end
+```
+
 ## API (library) usage
 
 ```ruby
-require 'docscribe/inline_rewriter'
+require "docscribe/inline_rewriter"
 
 code = <<~RUBY
   class Demo
@@ -354,135 +690,274 @@ code = <<~RUBY
   end
 RUBY
 
-# Insert docs (skip methods that already have a comment above)
+# Basic insertion behavior
 out = Docscribe::InlineRewriter.insert_comments(code)
 puts out
 
-# Replace existing comment blocks above methods
-out2 = Docscribe::InlineRewriter.insert_comments(code, rewrite: true)
+# Safe merge / normalization of existing doc-like blocks
+out2 = Docscribe::InlineRewriter.insert_comments(code, strategy: :safe)
+
+# Aggressive rebuild of existing doc blocks (similar to CLI -A)
+out3 = Docscribe::InlineRewriter.insert_comments(code, strategy: :aggressive)
 ```
 
 ## Configuration
 
-Docscribe can be configured via a YAML file (docscribe.yml by default, or pass --config PATH).
+Docscribe can be configured via a YAML file (`docscribe.yml` by default, or pass `--config PATH`).
+
+### Filtering
+
+Docscribe can filter both *files* and *methods*.
+
+File filtering (recommended for excluding specs, vendor code, etc.):
+
+```yaml
+filter:
+  files:
+    exclude: [ "spec" ]
+```
+
+Method filtering matches method ids like:
+
+- `MyModule::MyClass#instance_method`
+- `MyModule::MyClass.class_method`
 
 Example:
 
+```yaml
+filter:
+  exclude:
+    - "*#initialize"
+```
+
+CLI overrides are available too:
+
+```shell
+# Method filtering (matches method ids like A#foo / A.bar)
+docscribe --exclude '*#initialize' lib
+docscribe --include '/^MyModule::.*#(foo|bar)$/' lib
+
+# File filtering (matches paths relative to the project root)
+docscribe --exclude-file 'spec' lib spec
+docscribe --exclude-file '/^spec\//' lib
+```
+
+> [!NOTE]
+> `/regex/` passed to `--include`/`--exclude` is treated as a **method-id** pattern. Use `--include-file` /
+`--exclude-file` for file regex filters.
+
+Enable attribute-style documentation generation with:
+
 ```yaml
 emit:
-  header: true           # controls "# +Class#method+ -> Type"
-  param_tags: true       # include @param lines
-  return_tag: true       # include normal @return
-  visibility_tags: true  # include @private/@protected
-  raise_tags: true       # include @raise [Error]
-  rescue_conditional_returns: true  # include "@return [...] if Exception"
+  attributes: true
+```
+
+When enabled, Docscribe can generate YARD `@!attribute` docs for:
+
+- `attr_reader`
+- `attr_writer`
+- `attr_accessor`
+- `Struct.new` declarations
+
+### `attr_*` example
+
+> [!NOTE]
+> - Attribute docs are inserted above the `attr_*` call, not above generated methods (since they don’t exist as `def`
+    nodes).
+> - If RBS is enabled, Docscribe will try to use the RBS return type of the reader method as the attribute type.
+
+```ruby
+class User
+  attr_accessor :name
+end
+```
+
+Generated docs:
+
+```ruby
+class User
+  # @!attribute [rw] name
+  #   @return [Object]
+  #   @param [Object] value
+  attr_accessor :name
+end
+```
+
+### `Struct.new` examples
+
+Docscribe supports both common `Struct.new` declaration styles.
+
+#### Constant-assigned struct
+
+```ruby
+User = Struct.new(:name, :email, keyword_init: true)
+```
+
+Generated docs:
+
+```ruby
+# @!attribute [rw] name
+#   @return [Object]
+#   @param [Object] value
+#
+# @!attribute [rw] email
+#   @return [Object]
+#   @param [Object] value
+User = Struct.new(:name, :email, keyword_init: true)
+```
+
+#### Class-based struct
+
+```ruby
+class User < Struct.new(:name, :email, keyword_init: true)
+end
+```
+
+Generated docs:
+
+```ruby
+# @!attribute [rw] name
+#   @return [Object]
+#   @param [Object] value
+#
+# @!attribute [rw] email
+#   @return [Object]
+#   @param [Object] value
+class User < Struct.new(:name, :email, keyword_init: true)
+end
+```
+
+Docscribe preserves the original declaration style and does not rewrite one form into the other.
+
+### Merge behavior
+
+Struct member docs use the same attribute documentation pipeline as `attr_*` macros, which means they participate in the
+normal safe/aggressive rewrite flow.
 
+In safe mode, Docscribe can:
+
+- insert full `@!attribute` docs when no doc-like block exists
+- append missing struct member docs into an existing doc-like block
+
+### Param tag style
+
+Generated writer-style attribute docs respect `doc.param_tag_style`.
+
+For example, with:
+
+```yaml
 doc:
-  default_message: "Method documentation."
+  param_tag_style: "type_name"
+```
 
-methods:
-  instance:
-    public:
-      return_tag: true
-      default_message: "Public API. Please document purpose and params."
-  class:
-    private:
-      return_tag: false
+writer params are emitted as:
 
-inference:
-  fallback_type: "Object"
-  nil_as_optional: true
-  treat_options_keyword_as_hash: true
+```ruby
+#   @param [Object] value
 ```
 
-- emit.* toggles control which tags are emitted globally.
-- methods.<scope>.<visibility> allows per-method overrides:
-    - return_tag: true/false
-    - default_message: override the message for that bucket
-- inference.* tunes type inference defaults.
+With:
 
-### CLI
+```yaml
+doc:
+  param_tag_style: "name_type"
+```
+
+they are emitted as:
 
-```bash
-docscribe --config docscribe.yml --write lib/**/*.rb
+```ruby
+#   @param value [Object]
+```
+
+### Create a starter config
+
+Create `docscribe.yml` in the current directory:
+
+```shell
+docscribe init
+```
+
+Write to a custom path:
+
+```shell
+docscribe init --config config/docscribe.yml
+```
+
+Overwrite if it already exists:
+
+```shell
+docscribe init --force
+```
+
+Print the template to stdout:
+
+```shell
+docscribe init --stdout
 ```
 
 ## CI integration
 
-Fail the build if files would change:
+Fail the build if files would need safe updates:
 
 ```yaml
 - name: Check inline docs
-  run: docscribe --check lib/**/*.rb
+  run: docscribe lib
 ```
 
-Auto-fix before test stage:
+Apply safe fixes before the test stage:
 
 ```yaml
-- name: Insert inline docs
-  run: docscribe --write lib/**/*.rb
+- name: Apply safe inline docs
+  run: docscribe -a lib
 ```
 
-Rewrite mode (regenerate existing method docs):
+Aggressively rebuild docs:
 
 ```yaml
-- name: Refresh inline docs
-  run: docscribe --rewrite --write lib/**/*.rb
+- name: Rebuild inline docs
+  run: docscribe -A lib
 ```
 
 ## Comparison to YARD's parser
 
 Docscribe and YARD solve different parts of the documentation problem:
 
-- Parsing and insertion:
-    - Docscribe parses with Ruby's AST (parser gem) and inserts/updates doc comments inline. It does not reformat code
-      or produce HTML by itself.
-    - YARD parses Ruby into a registry and can generate documentation sites and perform advanced analysis (tags,
-      transitive docs, macros).
-
-- Preservation vs generation:
-    - Docscribe preserves your original source exactly, only inserting comment blocks above methods.
-    - YARD generates documentation output (HTML, JSON) based on its registry; it's not designed to write back to your
-      source.
-
-- Semantics:
-    - Docscribe models Ruby visibility semantics precisely for inline usage (including `class << self`).
-    - YARD has rich semantics around tags and directives; it can leverage your inline comments (including those inserted
-      by Docscribe).
-
-- Recommended workflow:
-    - Use Docscribe to seed and maintain inline docs with inferred tags/types.
-    - Optionally use YARD (dev-only) to render HTML from those comments:
-      ```shell
-      yard doc -o docs
-      ```
+- Docscribe inserts/updates inline comments by rewriting source.
+- YARD can generate HTML docs based on inline comments.
+
+Recommended workflow:
+
+- Use Docscribe to seed and maintain inline docs with inferred tags/types.
+- Optionally use YARD (dev-only) to render HTML from those comments:
+
+```shell
+yard doc -o docs
+```
 
 ## Limitations
 
-- Does not merge into existing comments; in normal mode, a method with a comment directly above it is skipped. Use
-  `--rewrite` to regenerate.
-- Type inference is heuristic. Complex flows and meta-programming will fall back to Object or best-effort types.
-- Ruby 2.7+ supported.
-- Inline rewrite is textual; ensure a clean working tree before using `--write` or `--rewrite`.
+- Safe mode only merges into existing **doc-like** comment blocks. Ordinary comments that are not recognized as
+  documentation are preserved and treated conservatively.
+- Type inference is heuristic. Complex flows and meta-programming will fall back to `Object` or best-effort types.
+- Aggressive mode (`-A`) replaces existing doc blocks and should be reviewed carefully.
 
 ## Roadmap
 
-- Merge tags into existing docstrings (opt-in).
-- Recognize common APIs for return inference (`Time.now`, `File.read`, `JSON.parse`).
-- Configurable rules and per-project exclusions.
-- Editor integration for on-save inline docs.
+- Effective config dump;
+- JSON output;
+- Overload-aware signature selection;
+- Manual `@!attribute` merge policy;
+- Richer inference for common APIs;
+- Editor integration.
 
 ## Contributing
 
-Issues and PRs welcome. Please run:
-
 ```shell
 bundle exec rspec
 bundle exec rubocop
 ```
 
-See CODE_OF_CONDUCT.md.
-
 ## License
 
 MIT