When Code Looks Fine but Isn’t: Building Nice Code for Evidence-Based Review

Description and use

Nice Code adds a review layer that surfaces contextual issues missed by compilers and linters, improving code review quality.

Problem

Pull requests can pass compilers, linters, and tests yet still contain serious engineering issues such as improper async handling, hidden credentials, or ignored errors.

Outcome

Nice Code surfaced contextual engineering questions early, reducing hidden bugs and improving review quality without replacing existing compilers or linters.

Workflow

• Install Nice Code via npm or npx
• Run "nice-code --changed --project ." during local development
• Optionally run "nice-code --all --project ." for full repo scans
• Use "nice-code --json" or "--format sarif" for machine-readable reports
• Integrate into CI with GitHub Actions to upload SARIF
• Create a baseline with "nice-code --write-baseline" to focus on new findings

Evidence

Nice Code adds a conservative, evidence-oriented review on top of the tools a project already uses.

Source

The baseline makes it possible to focus on new findings while the project works through older review items deliberately.

Source