pull-request

Generate Conventional Commit PR titles and summaries for staging branch merges.

14|Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Cogni-DAO/node-template --skill pull-request-cogni-dao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/Cogni-DAO/node-template/tree/main/.openclaw/skills/pull-request
Command: npx skills add https://github.com/Cogni-DAO/node-template --skill pull-request-cogni-dao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of Pull Request titles and summaries that adhere to the Conventional Commits specification, ensuring consistency and clarity in your project's commit history.

Core Features & Use Cases

  • Automated PR Title Generation: Creates titles following the type(scope): subject format.
  • Concise PR Summary: Generates factual summaries based on code changes.
  • Cohesion Check: Verifies that changes are related and belong to a single scope.
  • Use Case: Before merging a feature branch into staging, use this Skill to automatically generate a well-formatted PR title and summary that accurately reflects the changes, saving manual effort and improving review quality.

Quick Start

Use the pull-request skill to create a PR with a conventional commit title and summary into the staging branch.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I generate a conventional commit pull request title automatically?

Generate a conventional commit pull request title automatically by analyzing your branch changes. The tool enforces the type(scope): subject format and validates change cohesion before creating the title.

What is the best way to write a structured PR summary for a staging branch?

The best way to write a structured PR summary for a staging branch is to auto-generate a factual overview. The summary details context, changes, risk, rollout, and evidence based on the specific code modifications.

How does a conventional commit PR generator check code change scope?

A conventional commit PR generator checks code change scope by validating change cohesion before title generation. This ensures all modifications belong to a single scope and accurately reflect the branch diff.

Can I automate GitHub pull request descriptions to follow conventional commits?

You can automate GitHub pull request descriptions to follow conventional commits by generating strict standard titles and concise summaries. This enforces consistency and clarity in your project's commit history.

What should a conventional commit pull request summary include?

A conventional commit pull request summary should include structured context, changes, risk, rollout, and evidence. This factual breakdown accurately reflects the code modifications and improves review quality.

Why does my pull request title fail conventional commit validation?

Your pull request title fails conventional commit validation if the branch changes lack cohesion. The generator verifies that all modifications belong to a single scope before enforcing the strict title specification.