checkin

To verify code quality before a git commit, you can run a pre-commit check to validate build status, test results, code coverage, and security standards. This prevents unstable code from entering the repository.

Yes, you can enforce commit message conventions and branch naming automatically through workflow compliance checks. This ensures adherence to development standards before code is committed.

A pre-commit quality gate is an automated verification step for build status, test results, and documentation. You need it to prevent unstable or non-compliant code from being committed to your repository.

To prevent secrets from being committed, run a pre-commit security check. This scans your changes to ensure no sensitive data is included, maintaining a clean and secure commit.

No, the checkin skill has no external dependencies. It operates independently to verify your codebase stability and quality standards directly within your commit workflow.

If pre-commit checks are not passing, review the failed build status, test results, or code quality metrics. The skill identifies workflow compliance issues that must be resolved before committing.