Agent Skills › OpenSwiftUIProject/OpenSwiftUI › openswiftui-pr-authoring

openswiftui-pr-authoring

GitHub

用于起草或审查 OpenSwiftUI 项目的 Pull Request 标题和正文。遵循 Conventional Commits 规范，生成简洁、结果导向的英文描述，处理堆叠 PR 依赖关系，并管理远程操作权限确认。

.agents/skills/openswiftui-pr-authoring/SKILL.md OpenSwiftUIProject/OpenSwiftUI

Trigger Scenarios

创建新的 OpenSwiftUI Pull Request 审查或更新现有的 OpenSwiftUI Pull Request

Install

npx skills add OpenSwiftUIProject/OpenSwiftUI --skill openswiftui-pr-authoring -g -y

More Options

Non-standard path

npx skills add https://github.com/OpenSwiftUIProject/OpenSwiftUI/tree/main/.agents/skills/openswiftui-pr-authoring -g -y

Use without installing

npx skills use OpenSwiftUIProject/OpenSwiftUI@openswiftui-pr-authoring

指定 Agent (Claude Code)

npx skills add OpenSwiftUIProject/OpenSwiftUI --skill openswiftui-pr-authoring -a claude-code -g -y

安装 repo 全部 skill

npx skills add OpenSwiftUIProject/OpenSwiftUI --all -g -y

预览 repo 内 skill

npx skills add OpenSwiftUIProject/OpenSwiftUI --list

SKILL.md

Frontmatter

{
    "name": "openswiftui-pr-authoring",
    "description": "Draft or review public OpenSwiftUI pull request titles and bodies. Use when proposing, creating, updating, or reviewing an OpenSwiftUI PR."
}

OpenSwiftUI Pull Request Authoring

Write PR titles and bodies in English and scope them to the committed diff.
Use a concise Conventional Commits title that describes the outcome. Follow the contributor guide.
Use ## Summary for the main body. Start the first word of every summary bullet with a capital letter, and keep the bullets parallel and outcome-focused.
Omit build commands, test invocations, contributor-workflow boilerplate, remaining TODOs, and unrelated follow-up work.
Keep internal investigation methods out of public wording. Describe results in terms of compatibility, behavior, validation, or implementation.
For stacked PRs, describe only the current layer. Add a ## Stack section to a dependent PR and identify its direct dependency as Depends on #<number>.
Drafting a PR does not authorize pushing branches or creating or updating a PR. Present the title and body for review. Once the user explicitly approves the relevant remote actions, proceed without asking for the same approval again.