Ki^:UdZddlmZddlZddlZddlZddlZddlmZddl m Z eje Z dVdZddd d d d d dddddd d dddddd d ddddddd ddddddd dddd d!d d d"d#dd$dd d d%d&dd'ddd d(d)dd*dd d d+d,dd-dd d d. Zd/ed0<dWdXd1ZdYd2Z dZ d[d3Z d\ d]d4Zd5d6d7d8d9d:d;d8dd8d?d@dAd8dBZdCedD<d^d_dEZd`dFZdadGZdbdHZdIZedJZdcdKZdbdLZdMdNdOdPdQdRZdSedT<dddedUZy)fzClaude Code skills and hooks auto-install. Generates Claude Code agent skill files, hooks configuration, and CLAUDE.md integration for seamless code-review-graph usage. Also supports multi-platform MCP server installation. ) annotationsN)Path)Anyctjdk(r tjdz dz dz dz Stjdz dz dz S)z5Return the Zed settings.json path for the current OS.DarwinLibraryzApplication SupportZed settings.jsonz.configzed)platformsystemrhomed/home/jay/workspace/scripts/.codegraph-venv/lib/python3.12/site-packages/code_review_graph/skills.py_zed_settings_pathrsMH$yy{Y&)>>FXX 99; "U *_ <r!sDIIK($:]$Jr mcp_serverscLtjdz jS)Nrrrexistsrrrrr#s499;199;rtomlT)name config_pathkeydetectformat needs_typez Claude Codec |dz S)Nz .mcp.jsonrrs rrr)s D;$6r mcpServerscyNTrrrrrr+robjectCursorc|dz dz S)N.cursormcp.jsonrrs rrr1sD9$4z$ArcLtjdz jS)Nr-rrrrrr3s499;2::<rWindsurfc<tjdz dz dz S)N.codeiumwindsurfmcp_config.jsonrrs rrr9sDIIK*$rContinuec6tjdz dz S)N .continuez config.jsonrrs rrrIsDIIK+$= $MrcLtjdz jS)Nr=rrrrrrKs499;4<<>rarrayOpenCodec |dz S)Nz.opencode.jsonrrs rrrQs D+;$;rcyr(rrrrrrSr)r Antigravityc<tjdz dz dz S)N.gemini antigravityr4rrs rrrYsDIIK)$;m$KN_$_rcRtjdz dz jS)NrErFrrrrrr[s499;2]BJJLrz Qwen Codec6tjdz dz S)N.qwenr rrs rrrasDIIK'$9O$KrcLtjdz jS)NrIrrrrrrc499;088:rKiroc|dz dz dz S)N.kirosettingsr.rrs rrrisD7NZ$?*$LrcLtjdz jS)NrNrrrrrrkrKr) codexclaudecursorr3r continueopencoderFqwenkirozdict[str, dict[str, Any]] PLATFORMScttjdrdddgd}nddgd}|drd|d<|dk(rg|d <|S) z*Build the MCP server entry for a platform.uvxcode-review-graphserve)commandargsr$stdiotyperUenv)shutilwhich)platr!entrys r_build_server_entryrfrsZ ||E('2!  +I  Lf  je Lrc(t|tr(|jddjdd}d|dSt|tr|rdSdSt|trddj d |Dzd zSt d t|) z(Format a primitive Python value as TOML.\z\\"z\"truefalse[z, c32K|]}t|ywr7)_format_toml_value).0items r z%_format_toml_value..sJD1$7Js]zUnsupported TOML value: ) isinstancestrreplaceboollistjoin TypeErrorr`)valueescapeds rrnrns%--f-55c5A7)1~%v+G+%TYYJEJJJSPP .tE{o> ??rcd|d}d}|jr|jd}||vry|g}|jD]$\}}|j|dt |&dj |dz} |ry |j jd d d} |r.|jdr|n|dz} | jd s| dz } |j| | zdy ) zJAppend a Codex MCP server section without clobbering the rest of the file.z [mcp_servers.rrutf-8encodingFz =  Tparentsexist_okz ) r read_textitemsappendrnrxr:mkdirendswith write_text) r server_name server_entrydry_runsection_headerexisting section_linesr!rzsectionprefixs r_merge_toml_mcp_serverrs %[M3NH(('(: X %#$M"((*E UuC(:5(A'BCDEii &-GTD9 F%..t4(T/v& dNF6G+g> rcD|dk(rVtjDcic]\}}|ds||}}}d|vrK|dz jr8td|d<n+|tvrtj d|gS|t|i}g}|jD]E\}}|d|} |d} t ||} |d d k(rzt | d | | } | s)td |dd| |j|df|rtd|dd| ntd |dd| |j|di} | jr& tj| jd} |d dk(r}| j!| g}t#|t$sg}t'd|Dr*td |dd| |j|dFdd i| }|j||| | <n\| j!| i}t#|t(si}d |vr*td |dd| |j|d| |d <|| | <|rtd|dd| n\| j*j-dd| j/tj0| ddzdtd |dd| |j|dH|Scc}}w#tjtf$rtjd| i} YwxYw)aInstall MCP config for one or all detected platforms. Args: repo_root: Project root directory. target: Platform key or "all". dry_run: If True, print what would be done without writing. Returns: List of platform names that were configured. allr"rWrNzUnknown platform: %sr r!)r!r#rr[)rz rz: already configured in z [dry-run] z: would write z : configured r~rz#Invalid JSON in %s, will overwrite.r?c3hK|]*}t|txr|jddk(,yw)rr[N)rsdictget)ross rrqz+install_platform_configs..s.]TU:a&O155=( T/D/ : %[ *4S9 >V #,# G 4<.(@ NO!!$v,/ T&\N. NO4<. k]CD   d6l + $&     ::k&;&;W&;&MN >W $,,z2.Cc4(]Y\]]4<.(@ NO!!$v,/!4E EI JJy !#&HZ ll:r2Ggt,"g-4<.(@ NO!!$v,/+7G' (#*HZ  Lfn[MJ K    $ $TD $ A  " "4::hq#AD#HSZ " [ BtF|nM+? @$v,'}>(@ Y UP(('2 DkR sK$K$%K**1LLzExplore CodebasezDNavigate and understand codebase structure using the knowledge graphuB## Explore Codebase Use the code-review-graph MCP tools to explore and understand the codebase. ### Steps 1. Run `list_graph_stats` to see overall codebase metrics. 2. Run `get_architecture_overview` for high-level community structure. 3. Use `list_communities` to find major modules, then `get_community` for details. 4. Use `semantic_search_nodes` to find specific functions or classes. 5. Use `query_graph` with patterns like `callers_of`, `callees_of`, `imports_of` to trace relationships. 6. Use `list_flows` and `get_flow` to understand execution paths. ### Tips - Start broad (stats, architecture) then narrow down to specific areas. - Use `children_of` on a file to see all its functions and classes. - Use `find_large_functions` to identify complex code. ## Token Efficiency Rules - ALWAYS start with `get_minimal_context(task="")` before any other graph tool. - Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.)r descriptionbodyzReview ChangeszBPerform a structured code review using change detection and impactu## Review Changes Perform a thorough, risk-aware code review using the knowledge graph. ### Steps 1. Run `detect_changes` to get risk-scored change analysis. 2. Run `get_affected_flows` to find impacted execution paths. 3. For each high-risk function, run `query_graph` with pattern="tests_for" to check test coverage. 4. Run `get_impact_radius` to understand the blast radius. 5. For any untested changes, suggest specific test cases. ### Output Format Provide findings grouped by risk level (high/medium/low) with: - What changed and why it matters - Test coverage status - Suggested improvements - Overall merge recommendation ## Token Efficiency Rules - ALWAYS start with `get_minimal_context(task="")` before any other graph tool. - Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.z Debug Issuez?Systematically debug issues using graph-powered code navigationu## Debug Issue Use the knowledge graph to systematically trace and debug issues. ### Steps 1. Use `semantic_search_nodes` to find code related to the issue. 2. Use `query_graph` with `callers_of` and `callees_of` to trace call chains. 3. Use `get_flow` to see full execution paths through suspected areas. 4. Run `detect_changes` to check if recent changes caused the issue. 5. Use `get_impact_radius` on suspected files to see what else is affected. ### Tips - Check both callers and callees to understand the full context. - Look at affected flows to find the entry point that triggers the bug. - Recent changes are the most common source of new issues. ## Token Efficiency Rules - ALWAYS start with `get_minimal_context(task="")` before any other graph tool. - Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.zRefactor Safelyz;Plan and execute safe refactoring using dependency analysisuD## Refactor Safely Use the knowledge graph to plan and execute refactoring with confidence. ### Steps 1. Use `refactor_tool` with mode="suggest" for community-driven refactoring suggestions. 2. Use `refactor_tool` with mode="dead_code" to find unreferenced code. 3. For renames, use `refactor_tool` with mode="rename" to preview all affected locations. 4. Use `apply_refactor_tool` with the refactor_id to apply renames. 5. After changes, run `detect_changes` to verify the refactoring impact. ### Safety Checks - Always preview before applying (rename mode gives you an edit list). - Check `get_impact_radius` before major refactors. - Use `get_affected_flows` to ensure no critical paths are broken. - Run `find_large_functions` to identify decomposition targets. ## Token Efficiency Rules - ALWAYS start with `get_minimal_context(task="")` before any other graph tool. - Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.)zexplore-codebase.mdzreview-changes.mdzdebug-issue.mdzrefactor-safely.mdzdict[str, dict[str, str]]_SKILLSc||dz dz }|jddtjD]H\}}||z }d|dd|dd |d d }|j|d tj d|J|S)a^Generate Claude Code skill files. Creates `.claude/skills/` directory with 4 skill markdown files, each containing frontmatter and instructions. Args: repo_root: Repository root directory. skills_dir: Custom skills directory. Defaults to repo_root/.claude/skills. Returns: Path to the skills directory. .claudeskillsTrz --- name: rz description: rz --- rrr~rzWrote skill: %s)rrrrrinfo)r skills_dirfilenameskillpathcontents rgenerate_skillsrs*X5 TD1"==? -%H$ 6]O$!-012V}oR  !  '2 %t, - rc4ddddddgdgddd d dgdgd iS) u,Return Claude Code hook definitions for .claude/settings.json. Hooks use the v1.x+ schema: each entry needs a ``matcher`` and a nested ``hooks`` array. Timeouts are in seconds. ``PreCommit`` is not a valid Claude Code event — pre-commit checks are handled by ``install_git_hook``. hookszEdit|Write|Bashr]z%code-review-graph update --skip-flows)r`r]timeout)matcherrr}zcode-review-graph status ) PostToolUse SessionStartrrrrgenerate_hooks_configrs^  1%.'N')   "%.'A')    rcd}d}|dz }|jstjd|y|dz dz }|jj d |j rA|j d }||vr|S|j|jd d z|zd n|j|d |jd tjd||S)uGInstall a git pre-commit hook that prints a risk summary before each commit. Called automatically by ``code-review-graph install`` Creates ``.git/hooks/pre-commit`` if it doesn't exist, or appends to an existing one — preserving any hooks already there. Returns None when no ``.git`` directory is found. z#!/bin/sh # Installed by code-review-graph. Remove this file to disable pre-commit graph checks. if command -v code-review-graph >/dev/null 2>&1; then code-review-graph detect-changes --brief || true fi z code-review-graph detect-changesz.gitu<No .git directory found at %s — skipping git hook install.Nrz pre-commitT)rr~rrizWrote git pre-commit hook: %s) rrrr:rrrrrstripchmodr)rscriptmarkergit_dir hook_pathrs rinstall_git_hookrsF0F& G >> UW`a'!L0I D)&&&8 X  X__T2T9FBWUVg6 OOE KK/; rc|dz }|jdd|dz }i}|jr& tj|j d}t}|j||jtj|d d zdtjd |y#tj t f$r!}tjd||Yd}~d}~wwxYw) zWrite hooks config to .claude/settings.json. Merges with existing settings if present, preserving non-hook configuration. Args: repo_root: Repository root directory. rTrr r~rzCould not read existing %s: %sNrrrzWrote hooks config: %s)rrrrrrrrrrupdaterrr)r settings_dir settings_pathrexc hooks_configs r install_hooksrsy(Ltd3 ?2M!H Qzz-"9"97"9"KLH)*L OOL!TZZ;dBWU KK(-8$$g. Q NN;]C P P Qs%B33C- C((C-z$u ## MCP Tools: code-review-graph **IMPORTANT: This project has a knowledge graph. ALWAYS use the code-review-graph MCP tools BEFORE using Grep/Glob/Read to explore the codebase.** The graph is faster, cheaper (fewer tokens), and gives you structural context (callers, dependents, test coverage) that file scanning cannot. ### When to use graph tools FIRST - **Exploring code**: `semantic_search_nodes` or `query_graph` instead of Grep - **Understanding impact**: `get_impact_radius` instead of manually tracing imports - **Code review**: `detect_changes` + `get_review_context` instead of reading entire files - **Finding relationships**: `query_graph` with callers_of/callees_of/imports_of/tests_for - **Architecture questions**: `get_architecture_overview` + `list_communities` Fall back to Grep/Glob/Read **only** when the graph doesn't cover what you need. ### Key Tools | Tool | Use when | |------|----------| | `detect_changes` | Reviewing code changes — gives risk-scored analysis | | `get_review_context` | Need source snippets for review — token-efficient | | `get_impact_radius` | Understanding blast radius of a change | | `get_affected_flows` | Finding which execution paths are impacted | | `query_graph` | Tracing callers, callees, imports, tests, dependencies | | `semantic_search_nodes` | Finding functions/classes by name or keyword | | `get_architecture_overview` | Understanding high-level codebase structure | | `refactor_tool` | Planning renames, finding dead code | ### Workflow 1. The graph auto-updates on file changes (via hooks). 2. Use `detect_changes` for code review. 3. Use `get_affected_flows` to understand impact. 4. Use `query_graph` pattern="tests_for" to check coverage. cnd}|jr|jd}||vr!tjd|jy|r|j dsdnd}|rdnd}|j jdd|j||z|z|zdtjd |y) zAppend an instruction section to a file if not already present. Idempotent: checks if the marker is already present before appending. Creates the file if it doesn't exist. Returns True if the file was modified. r}r~rz+%s already contains instructions, skipping.FrTrz Appended MCP tools section to %s) rrrrrrr:rr) file_pathrrr separator extra_newlines r_inject_instructionsr5sH&&&8  A9>>R ):):4)@bI$D"M 4$7 I- =GRYZ KK2I> rc4t|dz tty)z&Append MCP tools section to CLAUDE.md.z CLAUDE.mdN)r_CLAUDE_MD_SECTION_MARKER_CLAUDE_MD_SECTION)rs rinject_claude_mdrMsK!r)rSrUrF)rF)rS)r3)rW)z AGENTS.mdz GEMINI.mdz .cursorrulesz.windsurfrulesz#.kiro/steering/code-review-graph.mdzdict[str, tuple[str, ...]]_PLATFORM_INSTRUCTION_FILEScg}tjD];\}}|dk7r||vr||z }t|tts+|j |=|S)uInject 'use graph first' instructions into platform rule files. Writes AGENTS.md, GEMINI.md, .cursorrules, and/or .windsurfrules depending on ``target``: - ``"all"`` (default): writes every file — matches pre-filter behavior. - ``"claude"``: writes nothing (CLAUDE.md is handled by ``inject_claude_md``). - any other platform key (``cursor``, ``windsurf``, ``antigravity``, ``opencode``): writes only the files associated with that platform. Returns list of filenames that were created or updated. r)rrrrrr)rrupdatedrownersrs rinject_platform_instructionsrbsbG7==?%& U?vV3 8# &?AS T NN8 $ % Nr)returnr)r})rddict[str, Any]r!rtrr)rzrrrt)F) r rrrtrrrrvrrv)rF)rrrrtrrvr list[str]r7)rrr Path | Nonerr)rr)rrrr)rrrNone)rrrrtrrtrrv)r)rrrrtrr) __doc__ __future__rrloggingr rbpathlibrtypingr getLogger__name__rrrX__annotations__rfrnrrrrrrrrrrrrrrrrrs#     8 $ =J; 6 A< ]J 8 >  M> ; _L K:  L:  SQ( $Qh& @  !   D\\ \\ \F#] . :![ . :X . 6"T . go& "od@"J#L96C34&5&R07!#+4 ;7r