菜单
Condense long commit logs, squash messages, or change narratives into 1–5 GitHub-ready markdown bullets with Conventional Commit subjects (≤50 chars). Use when the user asks to summarize a git log, boil down commits, write a squash-merge message, or produce a five-bullet PR/merge summary.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Extract a jargon-free ess-* shared package out of a team- or account-specific tool in a private repo and sync it to the open-source essentials repo, with deterministic scanners and an adversarial LLM reviewer in between. Use when the user runs /essentials-sync, asks to open-source a package, extract an ess-* package, move or sync a tool into essentials, or scrub a package of company jargon before publishing. Requires the essentials-sync CLI and a CURSOR_API_KEY.
Secure Cursor MCP credentials on macOS by moving secrets from ~/.cursor/mcp.json or a project .cursor/mcp.json into ~/.local/share/cursor-mcp/mcp.env and loading them via a LaunchAgent at login. Use when the user runs /mcp-hide-secrets, asks to secure MCP config, externalize MCP secrets, set up mcp.env, or fix MCP auth after cleaning up mcp.json. macOS only — do not use on Windows or Linux.
Address GitHub PR review comments on one or more PRs in parallel, each in its own git worktree on the PR's branch, reusing the pr-address-comments procedure. Auto-starts (look up PRs, create worktrees, fetch comments), then pauses to show a per-PR addressing plan for approval; after approval each PR is handled by a background subagent that implements, commits, pushes to the PR branch, and resolves threads. With no PR given, it discovers your own open PRs on the current repo's remote that have changes-requested or unresolved review comments and runs the same workflow. Use when the user gives one or more PR URLs/numbers, or asks to address/fix review comments on their own open PRs on this repo without naming them, especially in parallel or batch.
Read a remote GitHub PR's review comments, implement fixes on the PR branch, then reply to and resolve addressed threads (REST reply + GraphQL resolveReviewThread). Use for /pr-address-comments, a single PR URL or number, when not using the parallel batch skill pr-address-comments-all. Requires gh and a git checkout of the repo.
AI-assisted review of one or more GitHub Pull Requests. Offloads deterministic checks (lint, complexity, duplication, security, perf) to repo linters via self-contained scripts, then applies LLM judgment to what linters cannot catch and posts high-signal findings after a single human approval. Pass one or many PRs (numbers or URLs); with none, it discovers PRs where your review is requested. Use for /pr-review, "review PR <number/URL>", "review my requested PRs", "code review these pull requests". Requires gh and a git checkout.
| name | summarize-change-log |
| description | Condense long commit logs, squash messages, or change narratives into 1–5 GitHub-ready markdown bullets with Conventional Commit subjects (≤50 chars). Use when the user asks to summarize a git log, boil down commits, write a squash-merge message, or produce a five-bullet PR/merge summary. |
Turn a long git log, squash message draft, or PR narrative into 1–5 copy-paste markdown bullets for a GitHub merge commit or extended description.
Return only markdown bullets. No preamble, no section headings unless the user asks.
- **type(scope): subject** — One sentence: what changed and why it matters.
Co-authored-by: footers from the input only if present; place after bullets with a blank line before them.Follow Conventional Commits 1.0.0:
<type>[optional scope]: <description> — imperative mood, lowercase type.feat, fix, docs, refactor, perf, test, build, ci, chore.langsmith-client, azure-ai, hello-agent).Every subject must state what changed. Ban vague/process subjects:
| Bad | Good |
|---|---|
address PR #513 review comments | fix(langsmith-client): defer delete confirm |
port docs from #510 | docs(langsmith-client): document --deployment |
follow up on review | fix(hello-agent): align listener id messaging |
Before returning output, run from this skill's directory:
scripts/validate-summary.sh /tmp/draft-summary.md
Or validate the checked-in fixture:
scripts/validate-summary.sh \
examples-good.md
Or pipe stdin:
printf '%s\n' '- **fix: short subject** — Details.' \
| scripts/validate-summary.sh
The script enforces:
uv run cz check -m … -l 50 (explicit 50-char limit; config alone is not applied without -l)Fix every failure and re-run until exit 0. Only then return the markdown.
validate-summary.sh.validate-summary.sh)