ci_describe_pr

Generate a PR description from repository data and a template.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the generation of comprehensive PR descriptions by following the repository's pr_description.md template, reducing manual effort and ensuring consistent documentation across PRs.

Core Features & Use Cases

  • Template-driven PR descriptions aligned to thoughts/shared/pr_description.md
  • CI-friendly, non-interactive mode for automated environments
  • Syncs generated descriptions back to thoughts/shared/prs for traceability
  • Use Case: When a PR is opened in CI, automatically produce a complete description that reviewers can skim quickly.

Quick Start

Describe the active PR using the repository's pr_description.md template.

Frequently Asked Questions about ci_describe_pr

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

FAQPage Schema
How do I automatically generate a pull request description in CI workflows?

No, this skill is designed for CI-friendly, non-interactive automated environments. It directly fetches PR data and templates to generate descriptions without requiring interactive user input.

How does template-driven PR description generation work?

Template-driven PR description generation works by fetching the repository's pr_description.md template and grounding the output using the PR diff, commits, and base branch. It then saves the result to the thoughts/shared/prs directory and updates the PR body.

Can I sync generated PR descriptions back to my repository for traceability?

Yes, generated PR descriptions are synced back to the thoughts/shared/prs/{number}_description.md file. This ensures traceability while the PR body itself is also updated accordingly with the finalized text.

Does this PR description automation tool work without manual input in GitHub CI?

Yes, this skill operates in a CI-friendly, non-interactive mode ideal for GitHub workflows. When a PR is opened, it automatically produces a complete description that reviewers can skim quickly without manual intervention.

What should a PR description include for CI automated workflows?

An automated PR description should include a thorough summary grounded in the PR diff and commits, following the repository template. It synthesizes verification steps and a concise changelog to ensure consistent documentation for reviewers.