apply-review

You can automate applying code review findings as isolated commits by feeding a Findings-*.json file into this Skill, which validates the inputs and creates an atomic, one-shot commit for each individual finding.

Validating JSON findings before applying code changes works by checking your input file against a shared JSON schema, surfacing malformed inputs to the user to prevent bad data before any code modifications or commits are executed.

Yes, you can generate a structured audit report after applying code review findings because the Skill automatically produces an apply-report envelope designed specifically for downstream auditing and reporting tooling.

Yes, you need a specific JSON schema to apply code review findings automatically, as the Skill uses the jsonschema dependency to validate your Findings-*.json file and surface any issues before creating isolated commits.

The best way to create atomic commits for automated code fixes is to use a structured JSON findings file, which ensures each fix is validated and applied as a separate commit with an explicit message for precise auditing.

Applying JSON findings fails before any code changes are made because the Skill validates the input against a shared schema first, intentionally surfacing malformed data or structural issues to prevent invalid commits from entering your repository.