skills.rest
blakecyze
blakecyzeCOMMUNITY
Explore all skills by this author →
Website𝕏@cyze_devGitHub

kanso-pr

Generate pull request descriptions from commit history and repository templates.

2|Updated Apr 23, 2026
Search Tags:#automation#git#code review#documentation#pull request#github
One-click install
npx skills add https://github.com/blakecyze/kanso --skill kanso-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanso-pr
Source: https://github.com/blakecyze/kanso/tree/main/skills/kanso-pr
Command: npx skills add https://github.com/blakecyze/kanso --skill kanso-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh.

What problem does it solve?

This skill solves the issue of vague, unhelpful pull request descriptions that lack the necessary context for reviewers and future maintainers to understand the intent behind code changes.

Core Features & Use Cases

  • Automated Synthesis: Generates PR descriptions by pulling context directly from commit history, diff summaries, and repository templates.
  • Context Preservation: Ensures the "why" behind architectural decisions is captured, preventing knowledge loss.
  • Voice Calibration: Analyzes existing merged PRs to ensure the generated description matches the team's established tone and style.

Quick Start

Invoke the kanso-pr skill to draft a pull request description for the current branch based on the commit history and repository standards.

Frequently Asked Questions about kanso-pr

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

FAQPage Schema
How do I automatically generate pull request descriptions from git commit history?▼

You can automatically generate pull request descriptions by synthesizing commit history, diff summaries, and repository templates to bridge code changes with business intent. This approach captures the architectural reasoning behind modifications to prevent knowledge loss during code review.

Does this PR automation tool require GitHub CLI to analyze branch history?▼

Yes, generating context-aware PR descriptions requires both git and GitHub CLI integration. These dependencies allow the automation to analyze branch history, extract commit context, and facilitate the pull request creation process directly within your development workflow.

How do I match the tone of existing merged PRs when creating new pull request documentation?▼

You can match your team's established tone by analyzing existing merged pull requests to calibrate the generated documentation. This voice calibration ensures new PR descriptions align with repository-specific templates and maintain consistency across the codebase.

What is the best way to preserve architectural context in GitHub pull request descriptions?▼

The best way to preserve architectural context in pull request descriptions is to synthesize commit history and diff summaries automatically. This ensures the reasoning behind code changes is captured comprehensively, preventing knowledge loss for future maintainers.

Can I use this to automate PR creation for current branches based on repository standards?▼

Yes, you can automate PR creation for the current branch based on commit history and repository standards. By synthesizing commit context and applying repository-specific templates, it bridges the gap between code modifications and business intent.

Related Skills

Explore More Software Engineering Skills→
wyattjohwyattjoh
1

pr-create

Create and update GitHub pull requests from commit history and templates.

Community
Advanced
mvillmowmvillmow
18

gh-implement-issue

Automate GitHub issue implementation from branch creation to pull request.

Community
Intermediate
kzinmrkzinmr
7

requesting-code-review

Automate pre-commit code review with static analysis, security scanning, and automated fixes.

Community
Advanced
JsplixJsplix

code-review-pr-body

Generate structured pull request body drafts from git diffs.

Community
Intermediate