pr-draft-summary

Generate Conventional Commits-compliant PR titles and draft descriptions for node-redis changes.

17.6k|2.0k|Updated Sep 14, 2010
One-click install
npx skills add https://github.com/redis/node-redis --skill pr-draft-summary-redis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-draft-summary
Source: https://github.com/redis/node-redis/tree/main/.agents/skills/pr-draft-summary
Command: npx skills add https://github.com/redis/node-redis --skill pr-draft-summary-redis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating consistent, repo-compliant pull request summaries, titles, and descriptions for node-redis code changes is time-consuming and prone to missing key context like backward compatibility risks or untracked file changes.

Core Features & Use Cases

  • Automated Git Context Collection: Automatically gathers branch name, working tree status, changed files, diffs, and commit history without requiring user input.
  • Change Classification & Risk Flagging: Identifies change types (feature, fix, refactor, docs) and flags backward compatibility risks for modifications to public APIs, client behavior, or RESP wire handling.
  • Repo-Aligned PR Documentation: Generates Conventional Commits-compliant PR titles, branch name suggestions, and structured draft descriptions that follow node-redis contribution standards.
  • Use Case: After completing a fix for Redis cluster connection handling, this skill automatically pulls all modified runtime and test files, generates a fix: prefixed PR title, and drafts a description that notes the backward-compatible behavior adjustment.

Quick Start

Use the pr-draft-summary skill to generate a complete PR draft for your current node-redis code changes.

Frequently Asked Questions about pr-draft-summary

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

FAQPage Schema
How do I generate a pull request summary for node-redis changes?

To generate a pull request summary for node-redis changes, use this skill to automatically scan modified files, diffs, and commit history. It outputs repo-aligned PR titles, branch name suggestions, and structured draft descriptions.

What is conventional commits formatting for pull request titles?

Conventional commits formatting for pull request titles uses prefixes like fix: or feature: to classify changes. This skill applies repo-aligned conventional commits standards to automatically generate compliant PR titles for your node-redis contributions.

Can I automatically flag backward compatibility risks in my Redis client API changes?

Yes, you can automatically flag backward compatibility risks in Redis client API changes. This skill scans git diffs and commit history to identify public API modifications, client behavior shifts, or RESP wire handling changes that pose compatibility risks.

Does the PR draft generator require manual input for git context collection?

No, the PR draft generator does not require manual input for git context collection. It automatically gathers branch names, working tree status, changed files, and commit history directly from your local node-redis repository environment.

What is the best way to classify change types for node-redis code modifications?

The best way to classify change types for node-redis code modifications is using an automated skill that analyzes git diffs to identify features, fixes, refactors, or docs. It then maps these classifications to structured PR draft descriptions.