skills.rest
ZhaoyuWu
ZhaoyuWuCOMMUNITY
Explore all skills by this author →
GitHub

harness-pr-description

Generate PR descriptions with summary, changes, validation, risks, and rollback sections.

Updated Apr 18, 2026
Search Tags:#evidence#handover#generate#pull-request#pr-description#workflow-state
One-click install
npx skills add https://github.com/ZhaoyuWu/Website-Wzy --skill harness-pr-description
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-pr-description
Source: https://github.com/ZhaoyuWu/Website-Wzy/tree/main/codex-skills/harness-pr-description
Command: npx skills add https://github.com/ZhaoyuWu/Website-Wzy --skill harness-pr-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of reviewer-facing PR descriptions from workflow state, evidence, and handovers, reducing copy/paste errors and miscommunication.

Core Features & Use Cases

  • Generate reviewer-oriented PR sections based on workflow state, evidence, and handovers.
  • Include blockers, risks, validation checks, and rollback guidance.
  • Use case: When preparing a release, feed in the current state and handovers to automatically produce a complete PR description ready for review.

Quick Start

Provide the workflow state and handovers to generate a ready-to-paste PR description.

Frequently Asked Questions about harness-pr-description

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-generate PR descriptions from workflow state and evidence?▼

You can auto-generate PR descriptions by feeding workflow state, handovers, and evaluator results into a generation tool to produce a structured narrative with summaries, changes, and validation checks.

What should be included in a pull request description for code reviews?▼

A PR description for code reviews should include a summary, what changed, why it changed, validation checks, risks, fixes, and rollback guidance, all backed by workflow state and evidence.

How do I create evidence-backed PR narratives for release planning?▼

To create evidence-backed PR narratives during release planning, use handovers and evaluator results to automatically populate PR sections like validation, risks, and rollback guidance.

Can I automate PR handover documentation to reduce copy/paste errors?▼

Yes, automating PR handover documentation uses workflow state and evidence to generate reviewer-facing descriptions, eliminating manual copy/paste errors and reducing miscommunication.

Does generating PR descriptions require evaluator results and handovers?▼

Generating PR descriptions relies on workflow state, handovers, and evaluator results to produce a complete, structured PR narrative ready for review without manual input.

What's the best way to structure a PR description for reviewers?▼

The best way to structure a PR description for reviewers is using sections like summary, what changed, why, validation, risks, fixes, and rollback, generated automatically from workflow state.

Related Skills

Explore More Software Engineering Skills→
jolequesjoleques

answers-questions

Generates a Markdown report of answers to provided questions from given documentation files.

Community
Advanced
flosrnflosrn

create-pr

Create and push pull requests with auto-generated titles and descriptions.

Community
Intermediate
roycolumbia-coderoycolumbia-code

gsd-ai-integration-phase

Generate AI-SPEC.md design contracts and orchestrate workflow tasks.

Community
Advanced
sakastudiosakastudio

pr-create

Create a GitHub pull request from the current branch using gh pr create.

Community
Intermediate