validate

To validate generated project files for hardcoded secrets and absolute paths, use a security scanning process that checks for forbidden patterns, verifies well-formed JSON, and ensures required directories and valid hook scripts are present.

Checking if a settings.json hooks configuration conforms to the specification involves verifying the file structure against expected compliance standards to prevent configuration errors before deployment.

To automatically verify that required directories and command files exist after code generation, perform file validation checks that confirm the presence and well-formedness of all expected project outputs.

Yes, file validation for AI-generated outputs detects malformed JSON and invalid hook scripts by checking the existence and well-formedness of directories, command files, and configuration files.

You need to run compliance and security validation on generated configuration files immediately after an AI agent generates them, ensuring all files are correctly formatted and free of sensitive information before deployment.