一键在 Manus 中运行任何 Skill

开始使用

pr-summary

星标1

分支0

更新时间2026年2月4日 00:25

Generate pull request summaries and open GitHub PRs from the current branch’s git changes.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

win20

win20/dotfiles

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

PR Summary

Workflow

Analyze changes with git:
- git log main..HEAD --oneline
- git diff main...HEAD --stat
- If needed for clarity, read the full diff with git diff main...HEAD.
Draft a conventional-commit title:
- Format: <type>(<scope>): <summary> (<ticket>)
- Examples:
  - feat(profile): add blocking feature (HAE-111)
  - fix(onboarding): correct next button target path (HAE-222)
- If the ticket id or scope is unclear, ask for it before finalizing the title.
Generate a PR body with the exact structure below. Keep it concise, no extra text, and no “Generated with …” lines.
Create the PR using gh pr create with the title and body.

PR Body Template

## Summary

- [1-3 bullets describing the changes]

## Changes

- [Significant changes]
- [Files modified: list paths or key files]
- [Breaking changes, if any]

## Dependencies

- [Dependencies added or updated]

## Testing Notes

- [How to test these changes (ommit if not needed or if simple change)]

Notes

Keep all content factual and derived from the diff/log.
If there are no breaking changes or dependencies, write None rather than omitting the line.

同仓库更多 Skills

同仓库

git-commit

win20/dotfiles

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use whenever commiting changes to git.

2026-02-271

local-review

win20/dotfiles

Code reviews of git changes without creating actual PR.

2026-02-261

deep-plan

win20/dotfiles

Create thorough implementation plans for complex tasks.

2026-02-101

create-changelog

win20/dotfiles

Creates non-technical changelogs from git commits.

2026-02-041

create-prompt

win20/dotfiles

Rewrite user requests into clear, precise, and complete AI prompts. Use when a user asks to create, convert, or refine a prompt, or to restate a request as a specification for an AI model.

2026-02-041

documentation

win20/dotfiles

Create clear, concise technical documentation for a specified file, module, or folder.

2026-02-041

name	pr-summary
description	Generate pull request summaries and open GitHub PRs from the current branch’s git changes.

PR Summary

Workflow

Analyze changes with git:
- git log main..HEAD --oneline
- git diff main...HEAD --stat
- If needed for clarity, read the full diff with git diff main...HEAD.
Draft a conventional-commit title:
- Format: <type>(<scope>): <summary> (<ticket>)
- Examples:
  - feat(profile): add blocking feature (HAE-111)
  - fix(onboarding): correct next button target path (HAE-222)
- If the ticket id or scope is unclear, ask for it before finalizing the title.
Generate a PR body with the exact structure below. Keep it concise, no extra text, and no “Generated with …” lines.
Create the PR using gh pr create with the title and body.

PR Body Template

## Summary

- [1-3 bullets describing the changes]

## Changes

- [Significant changes]
- [Files modified: list paths or key files]
- [Breaking changes, if any]

## Dependencies

- [Dependencies added or updated]

## Testing Notes

- [How to test these changes (ommit if not needed or if simple change)]

Notes

Keep all content factual and derived from the diff/log.
If there are no breaking changes or dependencies, write None rather than omitting the line.