---
author: 'Andre Oliveira'
description:
  'Run the configured formatter and static checks for a scoped code change. Use
  after editing code or before a review; discover project commands rather than
  assuming a stack.'
extras:
  'Add `references/tooling.md` only for known project commands; add one eval for
  a repo without either folder.'
focus:
  'Run the repository’s configured formatter and static checks after a scoped
  code change.'
id: 'code-style-review'
improve:
  - 'Do not assume `backend/`, `frontend/`, Maven, ESLint, or Prettier exist;
    discover scripts from the current repository first.'
  - 'Separate safe formatting from semantic cleanup and require a diff review
    before broad auto-fixes.'
  - 'Add a small command-discovery script only if this project repeats the
    lookup.'
name: 'code-style-review'
path: '../submitted-skills/Andre%20Oliveira/skills/code-style-review/SKILL.md'
status: 'Good foundation'
title: 'Code style review'
wins:
  - 'Clear timing: after changes and before review.'
  - 'Includes a final evidence checklist.'
---

# code-style-review

## Inputs

Changed files and the repository root.

## Workflow

1. Inspect package/build configuration for the project’s documented lint,
   format, and style commands.
2. Run the narrowest relevant check first. Apply formatting only to the
   requested files unless the user asks for a wider change.
3. Review the diff for accidental rewrites, then rerun the same checks.

## Rules

- Do not invent directories or install tools without approval.
- Report unavailable checks as not run, not passed.
- Treat unused-code removal as a separate semantic change.

## Output

List each command, result, changed files, and any remaining failure.
