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

review-pr

Review all changes in a pull request or branch against its base branch. Use a knowledge graph, a map of code relationships, to report affected files and functions, test coverage, API compatibility issues, and recommended actions.

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

원문원문 설명 보기

Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.

설치 방법 보기

이럴 때 유용합니다

  • Reviewing all commits in a pull request
  • Checking a branch's changes against its base
  • Finding callers missed by public API changes
  • Summarizing impact and missing tests before merging

포함된 파일(1)

  • SKILL.md1.8 KB

SKILL.md(원문)

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

Review PR

Review all commits of a pull request or branch against its base branch.

Steps

  1. Identify the changes. With a branch name run git diff --name-only main...<branch>; otherwise diff the current branch against main (or master). Use that ref as base below.
  2. Call get_minimal_context_tool(task="review PR", base="main"). If it returns status: not_ready, call build_or_update_graph_tool() and continue.
  3. Call detect_changes_tool(base="main", detail_level="minimal") for risk-scored changed functions, test gaps and affected flows across the whole branch.
  4. For high-risk functions call query_graph_tool(pattern="callers_of", target="<function>") and query_graph_tool(pattern="tests_for", target="<function>"). Flag public API changes whose callers were not updated.
  5. Call get_review_context_tool(base="main") for source snippets, or get_impact_radius_tool(base="main") for the full dependent list, only when step 3 leaves a high-risk item unclear.
  6. Read the changed source of the highest-impact files first. Do not load whole files unless the change needs it.

Output

## PR Review: <title>

### Summary
<1-3 sentences>

### Risk
- Overall: Low / Medium / High
- Blast radius: <n> files, <m> functions
- Test coverage: <covered> of <changed> changed functions

### Files
#### <path>
- Changes: <what>
- Impact: <who depends on it>
- Issues: <bugs, style, concerns>

### Missing Tests
- <function> in <file>

### Recommendations
1. <action>

Tips

  • Use semantic_search_nodes_tool to find related code the PR may have missed.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Build or refresh a knowledge graph, a map of code relationships used for code review. Choose a full rebuild or an incremental update, then report the operation's status and summary.

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

  • Setting up the graph for a repository's first review
  • Refreshing the graph after switching branches
  • Updating review data after a large refactor
tirth8205/code-review-graph3.2만2026년 10월 16일 업데이트

Investigate bugs using a graph of code relationships. Find relevant functions, trace calls and execution paths, check recent changes, and assess what a proposed fix could affect before reading and changing the implementation.

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

  • Narrowing down code related to a bug
  • Tracing the execution path that triggers an issue
  • Checking whether recent changes caused a bug
tirth8205/code-review-graph3.2만2026년 10월 16일 업데이트

Explore an unfamiliar codebase using a graph of code relationships. Inspect its structure, find functions and classes, trace calls and imports, follow execution paths, and locate large functions for closer investigation.

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

  • Understanding the structure of an unfamiliar codebase
  • Finding functions and classes by name or keyword
  • Tracing calls, imports, and execution paths
tirth8205/code-review-graph3.2만2026년 10월 16일 업데이트

Plan refactoring with dependency analysis, which shows how code parts rely on each other. Find candidates and unreferenced code, preview and apply renames, and compare the resulting impact with the original plan.

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

  • Finding refactoring candidates and unreferenced code
  • Previewing edits before applying a rename
  • Checking affected dependencies and execution paths
tirth8205/code-review-graph3.2만2026년 10월 16일 업데이트

Review code changes using a knowledge graph, a map of code relationships, to assess risk and affected behavior. Organize findings by severity, identify missing tests, suggest fixes, and provide a merge recommendation.

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

  • Prioritizing review findings by risk
  • Checking how changed functions affect other code
  • Identifying missing tests and proposing test cases
tirth8205/code-review-graph3.2만2026년 10월 16일 업데이트

Review code changes against the previous commit and identify affected files and functions. Use dependency relationships to assess risk, check missing tests, and produce a focused report with issues and recommendations.

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

  • Reviewing changes against the previous commit
  • Checking how a change affects other functions
  • Finding missing tests for high-risk changes
tirth8205/code-review-graph3.2만2026년 10월 16일 업데이트

tirth8205의 스킬 모두 보기

이 스킬의 문제 신고