summarize-subsystemslisted

# Summarize subsystems (community summaries) Cluster the base code graph into subsystems (by module path) and write a short, **grounded** summary for each, persisted for `ask` / PR-walkthrough to use as a cheap high-level prior. This skill reads code and writes summaries to the reviewer store; it does NOT modify code or post to GitHub. **Always write summaries and answer the user in Russian** (the project language), regardless of this file's language. Tool calls, code identifiers and `path:line` stay verbatim. ## Tools <!-- include: _common/tool-usage.md --> Plus `list_subsystem_clusters`, `get_subsystem_summary_work`, `get_file_skeletons`, `index_subsystem_summary`, `prune_subsystem_summaries` and `backfill_summary_embeddings` (reviewer MCP). File-summary jobs read source ONLY through `get_file_skeletons`; the harness `Read` is not used on source files in this skill. ## Pipeline 1. **Resolve repo/branch.** <!-- include: _common/branch-selection.md --> 2. **List clusters (compact, paginated).** Walk every page: call `list_subsystem_clusters(repo, branch, compact=True, limit=100)`, then repeat with `offset += 100` while the response has `has_more == true`. Stop only when `has_more == false` — a partial walk is not a full pass. Empty / `note` about an empty index → tell the user (in Russian) to run `rag-reviewer:sync-codebase` first, then stop. Every page carries the same whole-set fields: `depth` (the applied cluster depth), `layout_token` (server-ow