跳到正文
cccskills
免费在 GitHub 公开

git-diff-summary

Analyze the current uncommitted diff and give a detailed summary with risk assessment. Use when asking what changed, reviewing changes before a commit, or requesting a change summary.

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

查看安装方法

包含的文件(1)

  • SKILL.md1.6 KB

SKILL.md(原文)

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

Staged changes

!git diff --staged --stat

Unstaged changes

!git diff --stat

Full diff

!git diff HEAD


Summarize the changes above:

1. What was modified and why

For each changed file, describe what was modified. Infer the intent from the diff — do not just list the line counts. Group related changes together if multiple files are part of the same logical change.

2. Risk factors

Flag any of the following if present in the diff:

  • Removed or weakened error handling (try/catch blocks deleted, error paths removed)
  • Changed public interfaces (function signatures, exported types, API response shapes)
  • Missing or removed tests for changed code
  • Hardcoded values where there were previously constants or configuration references
  • Security-sensitive areas touched (authentication, authorization, cryptography, input validation)
  • Dependency version changes
  • Database schema changes or data migrations

For each risk factor found, cite the specific file and line range.

3. Recommended next steps before committing

Based on the changes and any risk factors identified, give a prioritized list of things to do or verify before committing. Examples: "Run the test suite", "Add a test for the new error path in auth.ts:42", "Confirm the API response shape change is backward compatible".

If there are no risk factors and the changes are straightforward, say so clearly.

评价

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

评论

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

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

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.

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

davila7/claude-with-skills132026年5月15日 更新

REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.

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

davila7/claude-with-skills132026年5月15日 更新

Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.

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

davila7/claude-with-skills132026年5月15日 更新

Create a git branch named after a GitHub issue.

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

davila7/claude-with-skills132026年5月15日 更新

Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.

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

davila7/claude-with-skills132026年5月15日 更新

Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.

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

davila7/claude-with-skills132026年5月15日 更新

查看 davila7 的全部技能

报告此技能的问题