免费在 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.

中文简介正在准备中。当前显示原文说明。

lttr/claude-marketplace

集成工具Azure

查看安装方法

包含的文件（2）

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

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

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).

Form	Source
empty	current branch vs base (master/main)
`staged`	`git 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 PR	resolve work item → PR via `az boards`
path ending `.diff` or `.patch`	local diff file
anything else	treat 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.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

aiwork-protocol

免费

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.

中文简介正在准备中。当前显示原文说明。