authoring-extractors

Authoring custom error extractors lets you implement detect() and extract() hooks to reliably transform raw tool outputs into structured errors. This solves missing or garbled validation results when wiring support for new tools, languages, or build systems into your workflow.

To scaffold a new extractor for vibe-validate, run the command vv create-extractor <tool>. This generates the required custom detect() and extract() implementations and registers the plugin in the vibe-validate configuration so teams can reuse and share it.

An error extractor plugin translates raw tool outputs into a stable, structured error model during validation. You need one when validation reports failures but extraction is missing or garbled, or when wiring support for new tools, languages, or build systems.

Yes, custom extractors support new languages, build tools, and proprietary workflows. By leveraging the plugin system, you can author, test with fixtures, and share extractors to integrate tool outputs into vibe-validate workflows across teams and projects.

Error extraction is garbled when the built-in extractors cannot parse the raw tool output format. You must author a custom extractor with specific detect() and extract() implementations to reliably transform the tool output into structured errors.

Registration depends on your scaffolding workflow. Using vv create-extractor automatically scaffolds and registers the extractor in the vibe-validate config, while manually authored plugins require explicit configuration wiring to ensure reuse across projects.