dev-code-review

To review uncommitted git changes, you can run this skill in your project directory to analyze staged and unstaged code for style violations, potential bugs, and leftover debugging statements before committing.

A pre-commit code review evaluates pending git changes across five axes—style, correctness, completeness, comments, and dead code—to identify untracked unused symbols and leftover statements before they enter version control.

Yes, this pre-commit review applies across multiple programming languages, checking for best practices, file cleanliness, and potential issues in integration scenarios regardless of the specific tech stack.

The best way to check for bugs before a git commit is to perform an axis-based review of current git changes, evaluating code correctness, completeness, and adherence to project standards automatically.

Yes, you can use static analysis to flag leftover debugging statements, style violations, and untracked unused symbols by evaluating your uncommitted code changes before they are committed.

Running a pre-commit review ensures higher software quality and team consistency by automatically catching style violations, potential bugs, and dead code across your uncommitted changes, avoiding common pitfalls that manual checks miss.