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

code-review

Review code changes from current branch, an Azure DevOps PR, a git ref, or a diff/patch file. Trigger when user says "review this", "code review", "/df:code-review", or provides a PR id/URL, ticket URL, git ref, or diff path. Read-only — never posts comments.

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

연동 도구Azure
설치 방법 보기

포함된 파일(2)

  • SKILL.md3.8 KB
  • references/pipeline.md6.8 KB

SKILL.md(원문)

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

Code Review

Single entry point. Detect input source, produce a diff file, then run the review pipeline.

Input Detection

Argument is $ARGUMENTS (may be empty).

FormSource
emptycurrent branch vs base (master/main)
stagedgit diff --staged
numeric (12345)Azure DevOps PR id
URL containing _git/.../pullrequest/<id>Azure DevOps PR URL
URL containing _workitems/edit/<id> or ticket id mapped to PRresolve work item → PR via az boards
path ending .diff or .patchlocal diff file
anything elsetreat as git ref (branch / sha / tag)

Ambiguous → ask user. Do NOT guess.

Workflow

1. Resolve input → diff file path + metadata

empty

base=$(git rev-parse --verify master 2>/dev/null && echo master || echo main)
cur=$(git branch --show-current)
[ "$cur" = "$base" ] && abort "On base branch ($base). Switch to a feature branch."
git diff "$base"...HEAD > "/tmp/review-diff-$(date +%s).diff"
files=$(git diff --name-only "$base"...HEAD)
title="$cur"

staged

git diff --staged > "/tmp/review-diff-staged-$(date +%s).diff"
files=$(git diff --staged --name-only)
title="staged changes"

PR id / PR URL

Extract numeric id from URL if needed. Then:

az repos pr show --id <id> --output json
az repos pr diff --id <id> > "/tmp/review-diff-pr-<id>.diff"

Title/description/author/targetRefName from pr show output. Skip if status completed/abandoned, title has [WIP]/[Draft], author is bot, or only auto-generated files changed.

Work item / ticket URL

az boards work-item show --id <ticket-id> --expand relations -o json

Find related PR via relations of type ArtifactLink containing pullrequest. If multiple → ask user which. Then proceed as PR id.

.diff / .patch path

Use file as-is. Parse changed files from diff headers (+++ b/...).

git ref

git diff "<ref>"...HEAD > "/tmp/review-diff-ref-$(date +%s).diff"
files=$(git diff --name-only "<ref>"...HEAD)
title="HEAD vs <ref>"

2. Diff size guard

n=$(wc -l < <(echo "$files"))

If n > 50 → warn user, ask: proceed full / filter to paths / abort.

3. Run pipeline

Read references/pipeline.md and execute Phases 1–4 with:

  • DIFF_FILE = path from step 1
  • CHANGED_FILES = list from step 1
  • TITLE / META = title + (PR description, author, targetRefName) when available

4. Save output

If .aiwork/ protocol present, follow it. Otherwise:

slug=$(echo "$title" | tr '[:upper:]' '[:lower:]' | tr -cs 'a-z0-9' '-' | cut -c1-40)
mkdir -p ".aiwork/$(date +%F)_${slug}"

Save review markdown to .aiwork/{date}_{slug}/review.md. If a folder for this branch/ticket already exists, place it there.

Notes

  • Read-only. Never posts PR comments. For comments use pr-comments skill.
  • Pipeline detail lives in references/pipeline.md — load only when running review.
  • az repos pr requires the azure-devops az extension.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Structure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (intent, triage, research, spec, prd, areas, plan, review, notes, docs/). Use when the user asks to plan, capture an intent, make a spec, triage, research a task, write a report, code review, summarize findings, save the work, document decisions, record this, write that down, persist findings, or references any path under .aiwork/. Also use when starting a non-trivial task that needs a plan or spec before implementation, or when finishing one and capturing notes.

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

lttr/claude-marketplace22026년 10월 6일 업데이트

Use this skill when the user asks to test, verify, interact with, or automate web pages and browsers. Trigger for requests involving Chrome automation, browser testing, web scraping, screenshot capture, element selection, or checking web applications. Also trigger when user mentions "browser tools" explicitly.

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

lttr/claude-marketplace22026년 10월 6일 업데이트

changelog

무료

Show recent Claude Code changes personalized to user's setup. Trigger when user asks about changelog, "what's new", "cc changelog", "claude code updates", "recent changes", or wants to know what changed in Claude Code.

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

lttr/claude-marketplace22026년 10월 6일 업데이트

Review code changes from the current branch, staged changes, a git ref, or a diff/patch file. Pure git-native — no platform/PR awareness. Trigger when user says "review this", "review diff", "/aiwork:code-review-diff", or provides a git ref or diff path. Read-only — never posts comments.

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

lttr/claude-marketplace22026년 10월 6일 업데이트

Czech typography rules for web development. Use when building web pages in Czech language, writing Czech content, or fixing typography issues in Czech text. Covers punctuation, dashes, quotes, numbers, units, non-breaking spaces, and HTML entities.

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

lttr/claude-marketplace22026년 10월 6일 업데이트

Periodic dependency update run. Reads what the package manager says is outdated, upgrades what is safe, applies the code changes the new versions need, verifies, and opens one reviewable PR. Supports a read-only dry run that reports what it would do. Use when the user says "dependency update", "/dependency-update", "update deps", "dry run the dep update", or when a scheduled cloud routine fires.

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

lttr/claude-marketplace22026년 10월 6일 업데이트

lttr의 스킬 모두 보기

이 스킬의 문제 신고