원클릭으로 Manus에서 모든 스킬 실행

grape-oas-pr-description

스타8

포크4

업데이트2026년 4월 25일 23:49

Write a grape-oas PR description following the project's required template — Problem, Fix, Example (a minimal Grape API snippet), Schema before / after, Backward compatibility, optional Open questions. Use when the user asks for a PR body or commit-message-style summary on grape-oas changes, when running `gh pr create` for grape-oas, and in autonomous "fix the code and push a PR" workflows where the agent must produce the PR body without further user input. Output is a single Markdown block ready to paste into the PR body.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

numbata

numbata/grape-oas

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Generate a grape-oas PR description

Write a PR description for the diff in scope (current branch by default) following agents/pr-description.md.

Steps:

Inspect the diff. Default: git diff main...HEAD. If a different range is in scope, use that.
Identify which exporter / introspector / type-resolver paths are affected and which OAS versions (2.0, 3.0, 3.1) are impacted.
Write the PR body with all required sections in order: Problem, Fix, Example, Schema before / after, Backward compatibility, Open questions (optional).
The Schema before / after section is mandatory. If the change provably does not affect emitted output (a pure refactor, docs change, CI tweak), say so explicitly using the template from the "When the schema-before-after section can't be filled" section of agents/pr-description.md. Do not omit the section silently.
Use a minimal Grape API snippet (under ~15 lines) for the Example section. Strip everything not load-bearing.
Remind the user that the CHANGELOG entry lands after the PR is opened (it requires the PR number). Format: - [#N](https://github.com/numbata/grape-oas/pull/N): summary - [@<handle>](https://github.com/<handle>). under the appropriate ### Added / ### Fixed / ### Changed subsection of ## [Unreleased]. Danger warns when CHANGELOG.md is unmodified and fails when any line breaks Keep-a-Changelog format.

Do not include a test plan, "🤖 Generated with…" footers, or Co-Authored-By: Claude lines. Do not list every touched file. Do not restate the diff in prose.

Output the PR body as a single Markdown block. Do not commit or push anything.

이 저장소의 다른 Skills

같은 저장소

grape-oas-critique

numbata/grape-oas

Apply the grape-oas review checklist (six axes — schema correctness, test coverage, boundary violations, backward compatibility, CHANGELOG and PR body, code quality) when reviewing a working tree, branch, or PR in the grape-oas repository. Use when the user asks for a code review, critique, or audit on grape-oas changes — including before opening a PR, before committing, and in chained workflows where the agent reviews its own work before pushing. Output uses Block / Should fix / Consider / Nit severity labels and avoids invented findings.

2026-04-258

name	grape-oas-pr-description
description	Write a grape-oas PR description following the project's required template — Problem, Fix, Example (a minimal Grape API snippet), Schema before / after, Backward compatibility, optional Open questions. Use when the user asks for a PR body or commit-message-style summary on grape-oas changes, when running `gh pr create` for grape-oas, and in autonomous "fix the code and push a PR" workflows where the agent must produce the PR body without further user input. Output is a single Markdown block ready to paste into the PR body.
allowed-tools	Read Grep Glob Bash(git diff:) Bash(git log:) Bash(git status:*)

Generate a grape-oas PR description

Write a PR description for the diff in scope (current branch by default) following agents/pr-description.md.

Steps:

Inspect the diff. Default: git diff main...HEAD. If a different range is in scope, use that.
Identify which exporter / introspector / type-resolver paths are affected and which OAS versions (2.0, 3.0, 3.1) are impacted.
Write the PR body with all required sections in order: Problem, Fix, Example, Schema before / after, Backward compatibility, Open questions (optional).
The Schema before / after section is mandatory. If the change provably does not affect emitted output (a pure refactor, docs change, CI tweak), say so explicitly using the template from the "When the schema-before-after section can't be filled" section of agents/pr-description.md. Do not omit the section silently.
Use a minimal Grape API snippet (under ~15 lines) for the Example section. Strip everything not load-bearing.
Remind the user that the CHANGELOG entry lands after the PR is opened (it requires the PR number). Format: - [#N](https://github.com/numbata/grape-oas/pull/N): summary - [@<handle>](https://github.com/<handle>). under the appropriate ### Added / ### Fixed / ### Changed subsection of ## [Unreleased]. Danger warns when CHANGELOG.md is unmodified and fails when any line breaks Keep-a-Changelog format.

Do not include a test plan, "🤖 Generated with…" footers, or Co-Authored-By: Claude lines. Do not list every touched file. Do not restate the diff in prose.

Output the PR body as a single Markdown block. Do not commit or push anything.