# ryanmcdermott/code-review-tips

:microscope: Common problems to look for in a code review

Repository: https://github.com/ryanmcdermott/code-review-tips
Canonical: https://ross.abutalabs.com/products/code-review-tips
Language: JavaScript
License: MIT
License Family: permissive
Topics: code-review, review-tips, readability, javascript, review-process, reviews
Last push: 2023-02-27T07:26:42+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 3301, "days_push": 1283, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1527, forks 181 (observed 2026-08-28T04:04:58.536469+00:00)

## What it is
A curated guide of common problems to look for during code reviews, with JavaScript examples covering readability, side effects, security, performance, and testing. It is educational documentation rather than a runnable tool.

## Use cases
- learn what to look for when reviewing a pull request
- set up a code review checklist for my team
- improve code readability and naming in reviews
- train new engineers on the review process
- find common bugs before shipping features

## When to choose
- you want practical, example-driven guidance on reviewing code
- you are establishing or improving a team review process
- you need a reference checklist covering readability, security, and testing

## When to avoid
- you need an automated code review or static analysis tool
- you want a linter or formatter to enforce style rules
- you need language-specific review tooling rather than general advice

## Facets
- artifact type: learning-resource
- maturity: maintenance
- function: code-review, developer-tools, documentation
- domain: developer-tools, tutorials, testing
- platform: cross-platform
- tags: code-review-checklist, readability, javascript-examples, best-practices, engineering-culture

## Member repositories
- ryanmcdermott/code-review-tips (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:58.536469+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:31:34.534217+00:00, confidence not recorded.
  - readme: https://github.com/ryanmcdermott/code-review-tips (fetched 2026-08-28T04:04:58.536469+00:00, sha 77bc798983b9)
- Data as of 2026-08-30T08:39:29.467469+00:00.