360 Secure SkillHub
360 安全技能中心

pr-description

通过 git 读取当前分支相对基线分支的 diff 与提交列表,按固定模板(Summary、Changes、Testing、Notes / Follow-ups)整理出面向评审者的 Pull Request 描述草稿;要求先写变更结果、要点保持一行、说明意图与风险,无测试时需明确说明。

widoxm
widoxm
热度 42.41
最近更新 2026-08-31 20:25:39
分类:开发依赖:代码执行应用场景:代码审查 / 摘要总结 / 模板 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add widoxm/pr-description
Metadata
name
pr-description
description
Draft a pull request description from the current branch's diff. Use when the user asks for a PR description, a merge request summary, or "what does this change do".

PR Description

Generate a clear, review-friendly pull request description from the diff.

Workflow

  1. Get the diff against the base branch:
    • git diff <base>...HEAD (commits on this branch)
    • git log <base>..HEAD --oneline for the commit list
  2. Summarize the change set into a template.

Template

## Summary
<!-- One or two sentences: what this change does and why. -->

## Changes
<!-- Bullet list of the notable changes. -->

## Testing
<!-- How was this verified: commands run, tests, manual steps. -->

## Notes / Follow-ups
<!-- Anything a reviewer should know, or deferred work. -->

Rules

  1. Lead with the outcome, not a list of files — a reviewer reads this first.
  2. Keep bullets one line, imperative and specific.
  3. Do not restate the code; explain intent and any non-obvious decisions.
  4. Flag breaking changes and anything risky under "Notes".
  5. If there are no tests, say so explicitly rather than omitting the section.