跳到正文
cccskills
免费在 GitHub 公开

pr-summary

Summarize the current pull request including diff, comments, and review status. Use when reviewing a PR, preparing for a review meeting, or getting a quick PR overview.

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

集成工具GitHub
查看安装方法

包含的文件(1)

  • SKILL.md1.8 KB

SKILL.md(原文)

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

Pull request info

!gh pr view --json number,title,body,state,additions,deletions,changedFiles,reviews,statusCheckRollup

Changed files

!gh pr diff --name-only

Recent comments

!gh pr view --comments 2>/dev/null | tail -50


Summarize this pull request:

1. What problem it solves

From the PR title and body, describe what this pull request is trying to accomplish. Be specific — do not just restate the title.

2. What changed

From the changed files list and the additions/deletions counts:

  • How many files changed and roughly what areas of the codebase are affected
  • Whether this is a focused change (one feature, one bug fix) or a broad change touching many areas
  • Any files that stand out as high-risk or unexpected (e.g., changes to authentication, database migrations, public API files)

3. Unresolved comments or review concerns

From the comments section:

  • List any reviewer comments that appear to be unresolved (no response or no "resolved" marker)
  • Note any discussion threads that indicate disagreement or open questions

If there are no comments, say so.

4. Readiness to merge

Based on the review status and CI information from the JSON output:

  • Number of approvals vs requested changes
  • Whether required CI checks have passed, failed, or are still running
  • A one-sentence assessment: ready to merge, blocked by reviews, or blocked by CI

Do not make a merge decision — only summarize the current state. The final merge decision belongs to the user.

评价

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

评论

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

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

提交后会立即公开。请勿填写邮箱、电话等个人信息。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 的全部技能

报告此技能的问题