Marcos Silva
23 lines
870 B
Markdown
23 lines
870 B
Markdown
---
|
||
name: code-style-review
|
||
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.
|
||
---
|
||
|
||
# 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.
|