{"version":"2.1.323","anchor":"plugin-validate-output-reformatted-and-checks-engine-form","canonical_anchor":"plugin-validate-output-reformatted-and-checks-engine-form","heading":"Plugin validation output is grouped per module and checks module form","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-validate-output-reformatted-and-checks-engine-form","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Plugin validation output is grouped per module and checks module form\n\nPlugin validation now groups its details by module and reports when a module is not in the expected form\n\n**What**\n\nWhen Claude Code validates a plugin, its report is laid out differently. Details are now grouped under each module of the plugin instead of in one run.\n\nA new check also looks at the form of each module and prints a message when a module is not in the form Claude Code expects.\n\n**Why**\n\nThis only matters to people who write plugins. The grouped report makes it easier to see which module a problem belongs to.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}