review-code

To review git diffs for security vulnerabilities and PII leaks, the process analyzes staged changes to detect sensitive information like API keys, personal data, and internal paths. It automatically blocks commits that violate critical security rules before they reach the repository.

Enforcing coding standards automatically before a commit requires checking staged file changes against defined style guidelines like CodingStyle.md. This verifies formatting consistency and readability, blocking commits that fail to adhere to the specified standards.

Checking for security profile drift and CenCon documentation compliance involves analyzing code changes against expected architecture manifests. This ensures critical documentation exists, verifies new features are documented, and blocks commits lacking required coverage.

The code review process works directly with existing git diff and bash tools to perform comprehensive analysis. It reads file changes and executes bash commands to scan for security vulnerabilities, PII leaks, and style violations without requiring external dependencies.

Commits are blocked for missing documentation because the review process enforces documentation coverage for new tools and features. It checks for the existence and recency of critical manifests, ensuring all new capabilities are properly documented before integration.

Preventing the commit of sensitive internal paths requires scanning code changes for personal data and internal directory structures. The review process detects and flags these sensitive paths, blocking commits that violate critical security rules.