SkillsAdd

wilbeibi/wilbeibi-skills

newcomer-lens-review

Review code for rationale, domain terms, constraints, and assumptions missing to a newcomer, and produce a documentation backlog.

First seen May 12, 2026

Installation

$ npx skills add wilbeibi/wilbeibi-skills --skill newcomer-lens-review
View on skills.sh ↗ GitHub repository ↗

Summary

  • Review code for rationale, domain terms, constraints, and assumptions missing to a newcomer, and produce a documentation backlog.
  • Use when asked for an onboarding review, what would confuse a new hire, what a handover is missing, or which parts of a codebase need documenting first.
  • Do NOT use to find defects (use code-review) or to build your own understanding of unfamiliar code (use grok-repo).

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

azure-rbac Shared topics
microsoft/azure-skills 489K installs

Also in this package

Other skills from wilbeibi/wilbeibi-skills · top by installs.

npx skills add wilbeibi/wilbeibi-skills
test-writing 78 write-skill 76 skill-curator 76 complexity-budget 74 grill-me 74 karpathy-planning 71 repo-eval 70 web-recap 68 grok-repo 57 obsidian-capture 52

Browse all from wilbeibi/wilbeibi-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,691 B
  • docs SUMMARY.md 426 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 75 installs

SKILL.md

newcomer-lens-review

Review as a competent engineer who just joined: general engineering knowledge, but no project-specific context — design decisions, domain terms, historical constraints, team conventions.

Steps

  1. Read the diff or files. Mark every point where understanding requires information not present in the code.
  2. Categorize each gap (see "Gap categories" below).
  3. Produce findings first using the output contract below.
  4. Prioritize: top 3 gaps that most need documentation.

Context boundary

Assumed: language semantics, common algorithms, industry standard patterns. Not assumed: why this approach, project terminology, past attempts, implicit requirements, domain concepts.

Gap categories

  • Design rationale — why this algorithm/data structure/pattern over the obvious alternative?
  • Domain knowledge — what do project-specific terms mean? what business rules drive this?
  • Historical context — what's behind the TODO/workaround? why is approach X avoided?
  • System constraints — where does this timeout/limit/threshold come from? what failure modes?

Flag vs don't flag

Flag if a newcomer must:

  • Guess at unstated requirements.
  • Assume domain knowledge.
  • Infer from tribal knowledge.
  • Ask "why not the obvious alternative?"

Don't flag:

  • Standard language or framework usage.
  • Common industry patterns.
  • Anything inferable from immediate surrounding code.
  • Style preferences.

Output contract

  • Lead with Context gaps, grouped by file/component and ordered by onboarding risk.
  • Each finding names the category: design rationale, domain knowledge, historical context, or system constraint.
  • Add a short Critical for documentation list with the top 3 gaps.
  • Add Quick wins only for concrete fixes such as comments, names, constants, or doc links.
  • End with one line on what is understandable from the code. Omit praise.

Tone

Curious colleague asking genuine questions:

  • "What constraint makes X necessary here?"
  • "Is Y based on measurement or estimate?"
  • "I don't see why Z — what am I missing?"

Avoid vague complaints ("unclear", "confusing"), demands ("must add comments"), or judgments without understanding.