sanity-validators

Validate and sanitize untrusted strings by routing all user- or environment-derived inputs through domain-specific Sanitize* and Validate* helpers, enforcing correct string handling across code paths to prevent injection and unsafe usage.

String sanitization cleans untrusted inputs, while validation checks them against domain-specific predicates. Separating Sanitize* and Validate* helpers preserves correctness and establishes an explicit boundary between empty input rejection, per-domain character checks, and shell-metachar checks.

Enforce safe input handling by applying domain-specific predicates for identifiers, usernames, and file paths. This routing through dedicated validators prevents directory traversal, injection, and misinterpretation of untrusted config or CLI inputs.

Yes, this string validation approach applies across code paths that ingest strings from CLI flags, config files, and environment variables. It guides validators and sanitizers in the repo to prevent injection and unsafe usage.

The best way to document decision matrices for shell-metachar checks is to use a skill that imposes an explicit boundary between empty input rejection, per-domain char predicates, and separate shell-metachar checks, while providing a documented test strategy.

Separating empty input rejection from domain-specific character predicates imposes an explicit boundary that prevents common mistakes leading to injection. This structured validation decision matrix ensures correct string handling and safer code changes.