菜单
指导如何生成标准化的中文 PR 描述:通过比较当前分支与目标分支的差异,按照 Problem/Solution/Test Plan 格式生成结构化描述。 Use this skill to generate structured PR descriptions in Chinese using the Problem/Solution/Test Plan format based on git diff output.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
This skill should be used when the user asks to "create CLI", "setup Cobra", "add commands", "subcommands", "CLI flags", "Cobra with Viper", or works with command-line interface development in Go.
This skill should be used when the user asks to "setup ESLint", "configure ESLint", "lint TypeScript", "lint React", "ESLint rules", "code quality", or works with ESLint configuration for JavaScript/TypeScript/React projects.
This skill should be used when the user asks to "create GoFrame application", "setup GoFrame project", "GoFrame routing", "GoFrame middleware", "GoFrame API development", or works with GoFrame web framework components.
This skill should be used when the user asks to "setup golangci-lint", "configure linting", "Go code quality", "lint configuration", "CI linting", or works with Go code linting and quality tools.
This skill should be used when the user asks to "setup GORM", "GORM models", "GORM migrations", "database operations", "GORM associations", "GORM hooks", or works with database ORM operations in Go.
This skill should be used when the user asks to "setup Kind", "local Kubernetes", "Kind cluster", "multi-node cluster", "Kubernetes development", "k8s local environment", or works with local Kubernetes clusters using Kind.
基于 SOC 职业分类
| name | generate-pr-description |
| description | 指导如何生成标准化的中文 PR 描述:通过比较当前分支与目标分支的差异,按照 Problem/Solution/Test Plan 格式生成结构化描述。 Use this skill to generate structured PR descriptions in Chinese using the Problem/Solution/Test Plan format based on git diff output. |
为代码变更生成标准化的中文 Pull Request 描述,遵循 Problem/Solution/Test Plan 三段式格式。
PR 描述使用三段式结构:
# Problem
描述解决的问题或需求背景(1-3 句话)
# Solution
说明实现方案和关键变更(3-8 点)
# Test Plan
列出详细的人工测试步骤(3-8 步)
git diff 分析变更,聚焦核心变更点-)或小标题(###)1., 2., ...)git diff master...HEAD # 或 main...HEAD
从 diff 中识别:
回答:要解决什么问题?为什么需要改动?用 1-3 句话描述。
-)或小标题(###)组织1., 2., ...)编排 3-8 个测试步骤