Run any Skill in Manus with one click

pr-description

Stars228

Forks199

UpdatedApril 13, 2026 at 20:05

Prepare a pull request description from task artifacts under `tmp/tasks/<task-name>/` and the current implementation snapshot. Use when Claude needs to draft or refresh a Markdown PR description before review, handoff, or merge, including implementation summary, API changes, environment or configuration changes, database or migration impact, testing, and rollout notes.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

blockscout

blockscout/blockscout-rs

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	pr-description
description	Prepare a pull request description from task artifacts under `tmp/tasks/<task-name>/` and the current implementation snapshot. Use when Claude needs to draft or refresh a Markdown PR description before review, handoff, or merge, including implementation summary, API changes, environment or configuration changes, database or migration impact, testing, and rollout notes.
disable-model-invocation	true

PR Description Skill

Follow the workflow defined in @../../../.memory-bank/workflows/pr-description.md

Required Guardrails

Treat task artifacts as the source of truth for intended scope, then reconcile them against the current diff and changed files.
Write the artifact into the task folder as pr-description.md.
Keep the document reviewer-facing: explain what changed and why it matters, not a file-by-file changelog.
Include explicit sections for API changes and environment or configuration changes. If there are none, say None. instead of omitting the section.
Call out schema, migration, backfill, rollout, or operational impacts when they exist.
Summarize verification that actually happened. Do not claim tests or checks were run unless you verified that they were run.

Minimal Starting Reads

Start with:

../../../.memory-bank/project-context.md
../../../.memory-bank/architecture.md
../../../.memory-bank/gotchas.md
../../../tmp/tasks/<task-name>/task.md
../../../tmp/tasks/<task-name>/solution_*.md if present
../../../tmp/tasks/<task-name>/implementation-plan*.md if present
../../../tmp/tasks/<task-name>/coding-task*.md if present
../../../tmp/tasks/<task-name>/review.md if present

Then inspect the current diff, changed files, tests, migrations, config updates, and any API surface needed to describe the implemented change accurately.

More from this repository

same repository

implementation-plan

blockscout/blockscout-rs

Turn an approved task-analysis result into a shared technical design and coding-ready implementation handoff; use when Claude has an existing task folder under `tmp/tasks/`, plus a selected solution and related codebase research, and needs to produce `implementation-plan.md` and `coding-task.md` before writing code

2026-04-13228

research-scope

blockscout/blockscout-rs

Investigate and document the intended scope of a codebase topic through interactive discussion, then persist a durable research note under .memory-bank/research/ once the human confirms the framing

2026-04-13228

solution-review

blockscout/blockscout-rs

Review already-applied code changes against the original task statement or task folder artifacts under `tmp/tasks/<task-name>/`. Use when implementation work is done and Claude must verify scope coverage, detect mismatches or regressions, assess verification gaps, and write a review summary before handoff or merge.

2026-04-13228

task-analysis

blockscout/blockscout-rs

Review a task, issue, or feature request before coding; persist the task framing under `tmp/tasks/<task-name>/task.md`, write one or more `solution_N.md` option files, compare them in `solutions.md` when needed, and recommend a path with explicit reasoning

2026-04-13228

task-to-code

blockscout/blockscout-rs

Apply code changes from an existing task handoff under `tmp/tasks/<task-name>/coding-task-X.md`. Use when Claude receives a task name and coding-task index and must implement that prepared coding task strictly, without inventing missing scope or design details.

2026-04-13228

gh-issue-bug

blockscout/blockscout-rs

Draft a GitHub bug report from the current conversation, save it under tmp/gh-issues/, and follow the repository's canonical bug-report workflow.

2026-04-13228

name	pr-description
description	Prepare a pull request description from task artifacts under `tmp/tasks/<task-name>/` and the current implementation snapshot. Use when Claude needs to draft or refresh a Markdown PR description before review, handoff, or merge, including implementation summary, API changes, environment or configuration changes, database or migration impact, testing, and rollout notes.
disable-model-invocation	true

PR Description Skill

Follow the workflow defined in @../../../.memory-bank/workflows/pr-description.md

Required Guardrails

Treat task artifacts as the source of truth for intended scope, then reconcile them against the current diff and changed files.
Write the artifact into the task folder as pr-description.md.
Keep the document reviewer-facing: explain what changed and why it matters, not a file-by-file changelog.
Include explicit sections for API changes and environment or configuration changes. If there are none, say None. instead of omitting the section.
Call out schema, migration, backfill, rollout, or operational impacts when they exist.
Summarize verification that actually happened. Do not claim tests or checks were run unless you verified that they were run.

Minimal Starting Reads

Start with:

../../../.memory-bank/project-context.md
../../../.memory-bank/architecture.md
../../../.memory-bank/gotchas.md
../../../tmp/tasks/<task-name>/task.md
../../../tmp/tasks/<task-name>/solution_*.md if present
../../../tmp/tasks/<task-name>/implementation-plan*.md if present
../../../tmp/tasks/<task-name>/coding-task*.md if present
../../../tmp/tasks/<task-name>/review.md if present

Then inspect the current diff, changed files, tests, migrations, config updates, and any API surface needed to describe the implemented change accurately.