“EN-02-Code-Review-Debugging-Refactoring”

Map behaviors (not lines) to tests: which business rules, branches, and

Rank gaps by risk: money/auth/data-loss/permissions > complex branching >

Identify WEAK tests: no assertions, assertion-free mocks, tests that would pass

Write the top 5 missing tests (boundary + failure paths), table-driven, with

Recommend a realistic coverage policy: critical-package threshold + mandatory

Monolith-to-Module / Service Extraction Planner

Plans extraction of a bounded context from a monolith with data ownership and dual-write/cutover safety.

Bounded-context definition: domain language, owned data (exact tables/columns),

Target architecture: in-process module first (seams, interfaces), then optional

Data ownership migration: read model/API replacements for foreign readers,

Strangler steps as independently shippable PRs with feature flags, metrics for

Risks: distributed transactions avoided via saga/eventual consistency;

Docstrings/JSDoc: summary line (imperative), params/returns with units and

A module-level README section: responsibility, when to use/not use, key

Commit History / Changelog Writer

Writes Conventional Commits, PR descriptions, and user-facing changelogs from a diff — useful when preparing releases.

Conventional Commits if the change should be split (feat/fix/refactor/perf/

PR description: summary, motivation, approach, screenshots/API examples,

Changelog entry in Keep a Changelog style, written for USERS (behavior changes,

Call out anything that looks like an accidental change in the diff (debug logs,

Walk the execution path step by step with line refs; for each non-obvious

Highlight 3 things a junior would misunderstand, and ask me a checkpoint