error-standardizer

Convert nonstandard patterns like direct echoes, raw exits, and bare except blocks into a uniform emit_error() flow with named exit codes. This generates a guided standardization plan and updated files for review.

Nonstandard patterns include direct echoes to stderr, raw exit calls, bare except blocks in Python, and inconsistent error messaging. These cause brittle integrations and hard-to-trace failures across shell and Python sources.

Yes, you can enforce consistent error emission in CI pipelines by running standardization against your repository. It validates emitter sources, maps patterns to exit code constants, and outputs a safety-checked report.

Map detected patterns to standard constants and replace them with emit_error() calls. The process validates error emitter sources and generates a safety-checked report with updated files for review.

Yes, error standardization works with both shell and Python sources. It detects bare excepts in Python alongside direct echoes and raw exits in shell, converting them to emit_error() with named exit codes.

You need a repository with shell or Python sources and valid error emitter sources present. The standardizer validates emitter availability and maps patterns to exit code constants before generating updated files.