“EN-02-Social-Marketing-Commercial”

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),

Dependency analysis: inbound/outbound couplings (sync calls, shared DB joins,

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;

Code Comment / Documentation Improver

Turns bad comments into maintainable docs: explains WHY, keeps docs near code, and generates API docs from real signatures — no marketing fluff.

Remove/replace comments that restate code; convert every surviving comment into

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

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

Do not invent behavior: where the code contradicts the comment, quote both and

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,