review-and-fix

To run an unbiased code review on git changes, use a fresh-context sub-agent to analyze your current diffs without prior implementation knowledge. It identifies overlooked errors and automatically applies fixes to ensure code quality before committing.

A fresh-context code review analyzes code changes by simulating an external reviewer with no prior knowledge of implementation decisions. This unbiased approach catches overlooked errors and clarity issues that developers often miss when reviewing their own work.

Yes, you need git to perform automated code reviews because the skill relies on git diffing to detect current code changes. An optional CLAUDE.md file can also be provided to supply project-specific guidelines for the review.

You should run an automated code review after completing a new feature and before committing. This ensures potential bugs and clarity issues are objectively reviewed and automatically fixed before the code changes enter your project history.

Yes, you can use a CLAUDE.md file to provide project guidelines for code review. The skill reads this optional file to apply your specific project standards while performing unbiased analysis and automated refactoring on your git changes.