commit

To scan staged git changes for secrets before committing, this Skill reviews your Git diffs and status, automatically detecting insecure patterns like API keys or passwords, and blocks the commit execution if any secrets are found.

The best way to enforce conventional commit messages in git is to use a workflow tool that guides you through crafting clear commit messages and validates them against conventions before finalizing your staged code changes to the repository.

A secure git commit workflow handles code review by presenting staged modifications for user confirmation before execution, ensuring you review exactly what changed in your code before the commit is applied to the repository.

You can apply tiered validation to version control commits by configuring optional validation steps based on change tier, allowing the commit process to enforce different security and review rules depending on the modification scope.

A git commit would be blocked during version control when security scans detect secrets or insecure patterns within the staged code changes, preventing accidental exposure of sensitive data until the issues are resolved.

The commit workflow does not require any external dependencies to run, as it operates directly on Git diffs and status using internal scripts and references to manage security scans and commit message conventions.