anchor.diff:  }
   ----
   
  +[#mixin-annotation]
   ==== `@Mixin` Annotation
   A command defined in a class can include a mixin by annotating a field with `@Mixin`.
  -Similarly, a <<Subcommands as Methods,`@Command`-annotated method>> can include a mixin by declaring a `@Mixin`-annotated parameter.
  +Similarly, a <<Subcommands as Methods,`@Command`-annotated method>> can include a mixin by declaring a `@Mixin`-annotated method parameter.
   All picocli annotations found in the mixin class are added to the command (the "mixee").
   For example:
   
  
positive.code: 
  The GitHub project has a https://github.com/remkop/picocli/tree/master/picocli-examples/src/main/java/picocli/examples/mixin[full working example].
  
  ==== Adding Mixins Programmatically
  The below example shows how a mixin can be added programmatically with the `CommandLine.addMixin` method.
  
  
negative.code: You may be interested in the <<Executing Commands,execute method>> to reduce error handling and other boilerplate code in your application.
  See also the previous section, <<Executing Subcommands>>.
  
  [#parentcommand-annotation]
  === `@ParentCommand` Annotation
  In command line applications with subcommands, options of the top level command are often intended as "global" options that apply to all the subcommands. Prior to picocli 2.2, subcommands had no easy way to access their parent command options unless the parent command made these values available in a global variable.
  
  