df

GitHub

用于处理代码审查反馈,自动检查差异状态、读取评论并回复,解决或标记已处理意见,支持等待新反馈及定位代码位置。

skills/df/SKILL.md matheusfillipe/diffler

触发场景

用户说 check diffler 调用 /df 命令 请求查看审查评论

安装

npx skills add matheusfillipe/diffler --skill df -g -y
更多选项

不安装直接使用

npx skills use matheusfillipe/diffler@df

指定 Agent (Claude Code)

npx skills add matheusfillipe/diffler --skill df -a claude-code -g -y

安装 repo 全部 skill

npx skills add matheusfillipe/diffler --all -g -y

预览 repo 内 skill

npx skills add matheusfillipe/diffler --list

SKILL.md

Frontmatter
{
    "name": "df",
    "description": "Check the diffler review and respond to the human's feedback. Use when the user says \"check diffler\", invokes \/df, or asks to look at review comments."
}

Check the diffler review and respond to the human's feedback:

  1. Call the diffler MCP tool review_status for the active review and its changed files. If walkthroughs holds none about a change you made, call publish_walkthrough first (see /dfa), then continue. review_status names the repo; if it is not the repository you mean, call list_instances, then use_instance with that repo, and start over. If you changed files in another git repository, call open_project with its path, so the human reviews it as a tab beside this one; projects lists the ones already open.
  2. Call get_comments with status "open" and read each comment in place. Each carries a source: the human's review comments on the diff itself carry the diff's own source, while one starting walkthrough- is feedback on that walkthrough, a reply on one of its stops or notes.
  3. Address every comment in the code it anchors to.
  4. Answer each with reply_comment (what you changed and why), then propose_resolve to flag it addressed. That flag adds no text: do not summarise the answer you just gave. Only the human resolves for real, in the TUI.
  5. Call wait_for_feedback with the latest epoch and start over when it returns: the human just sent new feedback. It answers within 55 seconds; a timed_out result means they are still reviewing, so call it again. If the call itself fails, check review_status: diffler is closed only when that fails too, otherwise keep waiting.

Every diffler tool call already shows in the human's status bar. Before a stretch of work no tool call covers, such as editing the code a comment asks about, call report_activity with a few words for it.

When the human asks where something is, call focus to take them there: a comment or a walkthrough by its id, or a file and line in any review.

Write every reply like this

  • Say what you changed and why, in two to four short sentences or bullets. Lead with the change, then the reason.
  • Answer the question that was asked. If you disagree, say so in one sentence and say why.

Write for the card

Write for a narrow card beside the code:

  • Full sentences with their articles and pronouns, in the first person plural when we are the subject: "We changed X because Y." A sentence may also lead with the thing itself: "infra runs first because Y." Do not open every sentence the same way. Cutting words does not make text clearer.
  • Put every identifier in backticks: compute_overrides, SHEET_PERMISSIONS, MissingDecision. The card renders markdown; bare identifiers read as prose.
  • Plain verbs for code: raise, return, check, read, write, fail, skip. No metaphor: no gate, carry, land, surface, shape, vote, mint, unpick, wall, hold an opinion.
  • Comparing things, or listing data with several fields per item: a markdown table, header row, two to four columns, one row per thing, identifiers in backticks inside cells. The card rules the columns.

If the diffler tools are missing, the TUI isn't running: ask the human to run diffler in the repository first.

版本历史

  • 78ce09e 当前 2026-11-21 03:49

同 Skill 集合

skills/dfa/SKILL.md
skills/dfr/SKILL.md

元信息

文件数
0
版本
78ce09e
Hash
0cb170f2
收录时间
2026-11-21 03:49

首页 - Wiki
Copyright © 2011-2026 iteam. Current version is 2.156.0. UTC+08:00, 2026-11-21 05:03
浙ICP备14020137号-1