菜单
Summarise a git diff into a short change description, risk assessment, and suggested commit message. Use when the user asks to review changes, draft a commit message from a diff, or wants a high-level overview of what was edited.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Evaluate multiple choices side-by-side based on relevant criteria, then present a comparison the user can act on. Use when the user asks to compare options, choose between alternatives, or weigh up X vs Y.
Day-of-week rotating proactive sweep — Mon=connections / Tue=routines / Wed=skills / Thu=memories / Fri=findings / Sat=cross-cutting / Sun=weekly summary. Forces outward scan instead of inward thrash. Routine-only; load this skill into a daily routine that fires AssistantAgent. Adapted from goanna's caretaker.
Use when an agent has had N consecutive quiet runs with nothing to do. Pivots to bounded inward consolidation (promote findings, refresh memory, audit asks) anchored in own data — NOT generic news summarisation. Adapted from goanna's reverie cycle. Routine-only; loaded by the routine that detects the quiet condition.
Use to track open questions you owe the user (asks) and time-bounded commitments you owe yourself (tasks). Write OPEN entries when you commit; promote to CLOSED when answered/done. Survives session compaction. Adapted from goanna's asks.md/tasks.md pattern.
Reviewer criteria for AI-generated code via with_review. Checks for security issues (injection, auth bypass, secret leakage), correctness, and project conventions. Use as criteria.skill when generating code that touches data, auth, or external systems.
Reviewer criteria for outbound email drafts via with_review. Checks tone-recipient match, professionalism, no AI tells, no placeholder leakage. Use as criteria.skill argument when reviewing email drafts before send.
| name | git-diff-summariser |
| description | Summarise a git diff into a short change description, risk assessment, and suggested commit message. Use when the user asks to review changes, draft a commit message from a diff, or wants a high-level overview of what was edited. |
| compatibility | Works with any git diff text. No git access needed — the diff is provided as input. |
The user pastes or points at a git diff and wants a summary rather than reading it line-by-line.
Examples:
Get the diff content. Either the user pasted it, or they point at a file — use fs_read on a .diff / .patch file. If you have sandbox access and a git repo cloned in /workspace, the shell script below can regenerate the diff.
Run the bundled counter (optional quick-stats pass). This gives accurate line/file counts without the model having to count manually:
run_skill_script({
name: "git-diff-summariser",
path: "scripts/count.sh",
stdin: <the diff content>
})
Returns stdout like:
files_changed: 7
insertions: 142
deletions: 38
binary_files: 1
Read the diff yourself. The stats tell you the shape; now actually read the diff to understand what changed. Group changes by file or by logical theme (not by commit).
Produce four sections.
feat(module): …, fix(module): …, refactor(module): …)Offer next steps. offer_choices:
src/foo.ts not a/src/foo.ts.