describe_pr_nt

Generate pull request descriptions from diffs and commit history using gh CLI.

4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/visualitypl/visuality-humanlayer --skill describe-pr-nt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: describe_pr_nt
Source: https://github.com/visualitypl/visuality-humanlayer/tree/main/.github/skills/describe_pr_nt
Command: npx skills add https://github.com/visualitypl/visuality-humanlayer --skill describe-pr-nt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive pull request descriptions, ensuring consistency and adherence to repository templates, thereby saving developers time and improving the quality of PR documentation.

Core Features & Use Cases

  • Automated Description Generation: Creates detailed PR descriptions based on a predefined template.
  • Information Gathering: Automatically fetches PR diffs, commit history, and metadata using gh CLI.
  • Verification Step Handling: Attempts to run specified verification commands and documents their status.
  • Use Case: When you've finished coding a new feature, use this Skill to draft a complete PR description that includes what problem was solved, user-facing changes, implementation details, and verification steps, ready for review.

Quick Start

Use the describe_pr_nt skill to generate a description for the current pull request.

Frequently Asked Questions about describe_pr_nt

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

FAQPage Schema
How do I automatically generate a pull request description from my code changes?

You can automatically generate a pull request description by analyzing code diffs and commit history. This Skill gathers PR metadata via the gh CLI and populates repository-specific templates to create comprehensive documentation.

Can I use this to create PR descriptions that match my repository's specific template?

Yes, generating PR descriptions adhering to repository-specific templates is supported. It analyzes your code changes and formats the output to ensure consistency with your predefined project documentation standards.

Do I need the GitHub CLI installed to automate my PR documentation?

Yes, the GitHub CLI (gh) is required. The Skill depends on the gh CLI to automatically fetch pull request diffs, commit history, and metadata needed to draft the comprehensive descriptions.

What is the best way to document verification steps before merging a pull request?

The best way to document verification steps is to automate their execution and status reporting. This Skill attempts to run specified verification commands and includes their results directly in the generated pull request description.

What information is included in an automated GitHub pull request description?

An automated GitHub pull request description includes the problem solved, user-facing changes, implementation details, and verification steps. It compiles this information by analyzing your diffs and commit history.

Why should I automate drafting PR descriptions instead of writing them manually?

Automating PR descriptions saves development time and improves documentation quality by ensuring consistency. It eliminates manual effort by automatically gathering diffs and metadata to populate complete, template-compliant review summaries.