Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.
Install
npx skills add https://github.com/vercel/eve --skill gh-pr-descriptionSKILL.md
GitHub PR description
Inspect the branch diff, commits, related issue or discussion, tests, docs, and changesets. When updating a PR, read its current body first.
Write
Fill in .github/pull_request_template.md. Write for a reviewer, not a
changelog:
- Keep the Summary to one short paragraph: usually 2–4 sentences and about 100 words or fewer.
- Lead with the concrete problem, user need, or decision behind the change; follow with the solution and meaningful behavior. Prefer short sentences; split independent points rather than combining them into a long sentence.
- Do not list files or narrate commits. Include implementation detail only when it is necessary to assess behavior or risk.
- Mention breaking changes, preserved behavior, tradeoffs, scope boundaries, follow-ups, or stacked PRs only when they matter to review.
- Link an existing issue or discussion with
Closes #N,Related to #N, or an equivalent when one exists. Do not create an issue solely for a PR. - State only validation that actually ran, including limitations or failures.
Preserve the checklist and check only verified items.
Publish
Before publishing, confirm the Summary leads with why the change is needed.
Write the body to a file, then pass it to gh pr create or gh pr edit with
--body-file.
Related skills
domain-modelingmattpocock714KBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.to-specmattpocock576KTurn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.caveman-helpjuliusbrussee369KQuick-reference card for caveman modes, skills and commands. Trigger: /caveman-help or "caveman help".pptxanthropics228KUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the u