pr

GitHub

自动化准备并发布带有签名提交、动机说明和验证证据的草稿PR,规范PR描述结构并确保护理安全。

packages/eve-code/extension/skills/pr/SKILL.md vercel/eve

Trigger Scenarios

需要创建或更新Pull Request 要求生成符合规范的PR描述模板

Install

npx skills add vercel/eve --skill pr -g -y
More Options

Non-standard path

npx skills add https://github.com/vercel/eve/tree/main/packages/eve-code/extension/skills/pr -g -y

Use without installing

npx skills use vercel/eve@pr

指定 Agent (Claude Code)

npx skills add vercel/eve --skill pr -a claude-code -g -y

安装 repo 全部 skill

npx skills add vercel/eve --all -g -y

预览 repo 内 skill

npx skills add vercel/eve --list

SKILL.md

Frontmatter
{
    "name": "pr",
    "description": "Prepare and publish a draft pull request with a signed commit, motivation-led description, testable hypothesis, and validation evidence."
}

Publish a proposal

Fetch the current base immediately before publication. Rebase onto it, or replay only the intended diff onto a clean checkout when local commits are unavailable. Stop on conflicts, stale refs, unexpected paths, or unrelated reversions.

Stage only the intended changes. Repositories that require verified commits must use:

gh-signed-commit --repo owner/name --branch <branch> --base <base> -m "<headline>" [-b "<body>"]

The command commits only staged changes and synchronizes the checkout to the signed remote commit. Then write the PR body to a file and create one draft:

gh pr create --draft --title "<title>" --body-file <path> --base <base> --head <branch>

Use a specific title that names the behavior or problem. Never use placeholders such as prepare changes. Keep secrets, private context, credentials, and requester identity out of public metadata.

Write directly and top-down. Start with impact, then explain the essential decisions and why this shape tests the hypothesis. Prefer simple English and brief context over a wall of generated prose. Include truthful reproduction and validation evidence.

A useful description answers:

  1. Why the change is necessary.
  2. Why this approach is the smallest sound solution.
  3. Which entry points and data flows change.
  4. What evidence verifies the expected outcome.

Prefer this shape unless the repository has a required template:

[One-line summary of what changed and why]

**Why**

[Observed problem, evidence, and impact]

**Approach**

Because [cause], changing [mechanism] should [expected outcome].

**Validation**

[Focused checks and results]

**Relevant context**

[Only the implementation or data-flow details reviewers need]

Version History

  • a6ae201 Current 2026-09-27 14:55

Same Skill Collection

.agents/skills/gh-pr-description/SKILL.md
.agents/skills/human-writing/SKILL.md
.agents/skills/technical-writing/SKILL.md
.agents/skills/test-audit/SKILL.md
packages/eve-code/extension/skills/investigate/SKILL.md
packages/eve-code/extension/skills/lookup-agent-run/SKILL.md
packages/eve-code/extension/skills/review/SKILL.md
SKILL.md
skills/eve/SKILL.md

Metadata

Files
0
Version
a6ae201
Hash
1fc6e0a8
Indexed
2026-09-27 14:55

ホーム - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-09-29 20:04
浙ICP备14020137号-1