_change-summary

Generate commit summaries from git history for PR descriptions.

2|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/wxy/SilentFeed --skill change-summary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _change-summary
Source: https://github.com/wxy/SilentFeed/tree/main/.copilot/skills/_change-summary
Command: npx skills add https://github.com/wxy/SilentFeed --skill change-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

自动汇总当前分支相对主分支的提交摘要,帮助开发者快速生成清晰、完整的 PR 描述,减少遗漏关键改动。

Core Features & Use Cases

  • 自动提要:从 git log --oneline origin/master..HEAD 生成变更摘要。
  • 一致性检查:将摘要对齐到项目的提交说明模板。
  • 快速应用场景:在提交前快速生成 PR 描述或变更日志。

Quick Start

运行本工具以生成当前分支相对主分支的提交摘要,并将结果写入 PR 描述。

Frequently Asked Questions about _change-summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a PR description from git commit history?

To generate a PR description from git commit history, this Skill automates summarizing commits between origin/master and HEAD into a concise '提交摘要' section, ensuring clear pull request descriptions aligned with project guidelines.

What is the best way to summarize commits for a pull request?

The best way to summarize commits for a pull request is to automatically extract commit logs from origin/master..HEAD and format them into a structured summary, preventing the omission of key changes in your PR description.

How do I create a change-log from my current branch?

To create a change-log from your current branch, the Skill processes git log --oneline origin/master..HEAD to automatically generate a concise summary of all new commits, which can then be directly written into your PR description.

Can I automatically align PR descriptions with project commit templates?

Yes, you can align PR descriptions with project commit templates because the Skill includes a consistency check feature that formats the generated commit summary to match your specific project guidelines.

What happens when generating a commit summary with no new commits?

When generating a commit summary with no new commits, the Skill gracefully handles the edge case by recognizing the empty state between origin/master and HEAD, avoiding errors and ensuring the PR process remains stable.

Does this tool work for updating existing PR descriptions across branches?

Yes, the tool works for updating existing PR descriptions across branches, applying its automated commit summary generation to both creating new pull requests and updating current ones relative to the master branch.