본문으로 건너뛰기
cccskills
무료GitHub에 공개

code-graph

Explore relationships between functions and files using a prebuilt code graph, a map of code dependencies. Trace bugs, inspect callers and execution paths, and assess the impact of refactoring or proposed changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Query the pre-built code-review-graph knowledge graph (Tree-sitter, whole monorepo) instead of walking call chains with Grep+Read – 2-6x cheaper, and it catches dynamic dispatch that grep misses. Use for ANY task that spans multiple files, even when the user never mentions a graph or asks for it - fixing or tracing a bug ("fix this bug", "why does X happen", "trace this"), exploring unfamiliar code ("how does X work", "who calls X", "what imports Y", "where is X used or handled"), planning or doing a refactor ("rename X", "is it safe to change or remove X", "what would break", "blast radius", "find dead code"), or reviewing changes ("review this PR", "review this branch or diff"). When you are about to Grep for a symbol's callers, callees, or importers, use this skill.

설치 방법 보기

이럴 때 유용합니다

  • Explore callers and dependencies in unfamiliar code
  • Trace a bug across multiple files
  • Assess the impact of renaming or removing code
  • Review changes by risk and test coverage

포함된 파일(1)

  • SKILL.md3.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Code graph (code-review-graph MCP)

Four modes (explore, debug, refactor, review) share the same setup and tools. Full setup, version pin, rebuild, troubleshooting: .ai/MCP.md ("code-review-graph MCP").

Bootstrap once per session

Graph MCP tools are deferred, so a direct call fails with InputValidationError. Load schemas first with one ToolSearch (comma-separate the tools the task needs):

ToolSearch query: "select:mcp__code-review-graph__query_graph_tool,mcp__code-review-graph__get_impact_radius_tool,mcp__code-review-graph__detect_changes_tool,mcp__code-review-graph__get_affected_flows_tool"

Keep the graph current

A graph built on another branch makes detect_changes report function names from unrelated files. The PostToolUse hook syncs after edits; rebuild manually after git checkout / git pull / large merges:

pipx run code-review-graph==2.3.6 status
pipx run code-review-graph==2.3.6 build

Modes

Explore

  1. list_graph_stats, then list_communities and get_community.
  2. semantic_search_nodes finds a function or class by name (keyword match).
  3. query_graph with callers_of / callees_of / importers_of / children_of.
  4. list_flows and get_flow for execution paths.

Debug

  1. semantic_search_nodes for code related to the symptom.
  2. query_graph callers_of and callees_of; the triggering entry point is usually upstream.
  3. get_flow through suspect areas; get_impact_radius on suspect files.
  4. Verify the branch, then detect_changes (recent changes are the most common cause).

Refactor

  1. get_impact_radius and get_affected_flows before touching code.
  2. refactor_tool mode rename previews every affected location; dead_code finds unreferenced code; suggest proposes community-driven splits.
  3. apply_refactor_tool with the refactor_id applies a previewed rename.
  4. detect_changes afterwards.

refactor_tool, apply_refactor_tool, and find_large_functions are not validated on this codebase: treat output as hypotheses, verify each edit against the code, and preview before applying.

Review

  1. detect_changes (risk-scored), get_affected_flows, get_impact_radius.
  2. Test coverage: grep for *.spec.js / *.unit.js (tests_for returns 0 incorrectly for many files). Suggest cases for untested changes.

Report grouped by risk (high/medium/low): what changed and why it matters, test-coverage status, suggested improvements, overall merge recommendation.

Cross-cutting rules

  • Pass detail_level: "minimal" (standard mode inflates tokens ~6x).
  • Use fully qualified names: path/to/file.ts::ClassName.methodName; bare names return "ambiguous".
  • Use list_communities + get_community in place of get_architecture_overview (~3.9M characters, overflows context).
  • Grep is cheaper than children_of for single-file structure.

Target: any graph task in 5 tool calls or fewer.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Develop and modify the Handsontable Angular wrapper with guidance on component lifecycle, settings updates, and NgZone, which controls change detection. It also covers standalone examples, global configuration, and the build and test workflow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Fix settings updates in the Angular wrapper
  • Review change detection around grid operations
  • Update examples to standalone components
handsontable/handsontable2.2만2026년 10월 19일 업데이트

Open local or public web pages in BrowserStack Live for checks on real mobile devices or desktop browsers. The skill prepares temporary access to a local server, launches the requested session, and shares its dashboard link.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Check a local page on an Android device
  • Open a page in Safari on an iPhone or iPad
  • Inspect behavior in a specific desktop browser
handsontable/handsontable2.2만2026년 10월 19일 업데이트

Prepare user-facing changelog entries for source code changes. The skill determines whether an entry is needed, classifies the change, writes a clear title, and uses the project CLI to create a JSON file tied to the pull request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Add a changelog entry for a bug fix
  • Classify a new feature or behavior change
  • Explain a breaking change and its replacement
handsontable/handsontable2.2만2026년 10월 19일 업데이트

Work with Handsontable row and column positions by distinguishing source data, displayed order, and rendered cells. It guides index conversion and helps investigate misplaced data when sorting, filtering, hiding, or moving rows and columns.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigating misplaced rows or columns
  • Converting between source and displayed indexes
  • Combining filters with manual column movement
handsontable/handsontable2.2만2026년 10월 19일 업데이트

Create Handsontable documentation examples for JavaScript, TypeScript, React, Angular, and Vue. The skill explains source files, generated JavaScript, required imports and license settings, embedding examples in guides, and checking that each framework version displays correctly.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding a code example to a feature guide
  • Preparing examples for multiple frameworks
  • Generating JavaScript examples from TypeScript
handsontable/handsontable2.2만2026년 10월 19일 업데이트

Build Handsontable demo pages for visual regression tests, which compare screenshots for appearance changes. It guides feature routes, URL-driven display states, sample data, and decisions about testing the same feature across framework wrappers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding a demo route for a new feature
  • Creating multiple visual states through URL parameters
  • Planning visual coverage across framework wrappers
handsontable/handsontable2.2만2026년 10월 19일 업데이트

handsontable의 스킬 모두 보기

이 스킬의 문제 신고