“React”

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.

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,

"Explain This Code" Tutor (Socratic)

Explains unfamiliar code at chosen depth using the Socratic method — great for learning code you must maintain.

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

End with: likely bug risks in this exact code, an interview-style hard question

对话与命令生成：侧边栏对话可附加工作区上下文，斜杠命令（/explain、