describe_pr_nt

Generate PR descriptions from a built-in template using PR metadata.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill describe-pr-nt-brightblock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: describe_pr_nt
Source: https://github.com/BrightBlock/hyprlayer-cli/tree/main/claude/skills/describe_pr_nt
Command: npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill describe-pr-nt-brightblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate comprehensive PR descriptions automatically using a built-in template, eliminating ad-hoc drafting and ensuring consistency across PRs.

Core Features & Use Cases

  • Template-driven PR descriptions that cover problem, changes, testing, and changelog.
  • Works for repositories lacking an existing pr_description.md template or when standardization is required.
  • Integrates with PR tooling to pull metadata and ensure the description aligns with the team's workflow.

Quick Start

Describe a PR using the built-in template and save the result to /tmp/pr_description.md

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 PR description with a standard template?

Generate a PR description automatically by applying a built-in template that structures problem context, code changes, testing details, and changelog notes into a unified format, saving the result to a temporary markdown file for syncing with the repository.

What's the best way to standardize PR descriptions across multiple GitHub repositories?

Standardize PR descriptions across multiple GitHub repositories by applying a built-in template that uniformly formats problem statements, changes, testing, and changelog details, which is especially useful when repositories lack an existing pr_description.md template.

Can I pull PR metadata like title and base branch into the generated description?

Pull PR metadata like title, number, URL, and base branch into the generated description by integrating with PR tooling, which extracts the repository context to ensure the final template output aligns with the team workflow.

Does this work for repositories lacking an existing pr_description.md template?

It works for repositories lacking an existing pr_description.md template by supplying a built-in template that ensures consistent PR documentation, applying whenever a standardized format is required across multiple pull requests.

How do I include verification notes and changelog details in my GitHub PR descriptions?

Include verification notes and changelog details in GitHub PR descriptions by using a template-driven generation process that automatically structures these sections alongside problem and testing information into the final synced description.

When should I avoid using a template to generate PR descriptions?

Avoid using a template to generate PR descriptions when your repository already enforces a custom pr_description.md format or when a specific pull request requires a highly ad-hoc, non-standardized drafting approach that deviates from the built-in changelog and testing structure.