git-pr

Generate and update pull request titles and descriptions from git diffs and commit logs.

2|Updated Jan 13, 2026

Search Tags:#automation #git #devops #code review #pull request #github

Ready to run

npx skills add https://github.com/erclx/aitk --skill git-pr-erclx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-pr
Source: https://github.com/erclx/aitk/tree/main/claude/skills/git-pr
Command: npx skills add https://github.com/erclx/aitk --skill git-pr-erclx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the manual overhead and inconsistency of writing pull request descriptions, ensuring that PRs accurately reflect the actual code changes rather than just the developer's intent.

Core Features & Use Cases

Automated PR Generation: Derives titles and bodies directly from git diffs and commit history, excluding lockfiles for cleaner reviews.
In-place Synchronization: Automatically detects existing pull requests and updates them when new commits are pushed, preventing duplicate PRs.
Standardized Testing: Enforces strict testing discipline by requiring verification of results before checking off boxes in the PR body.

Quick Start

Run the git-pr skill to generate or update the pull request for your current branch based on the latest diff against main.

Frequently Asked Questions about git-pr

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

FAQPage Schema

How do I automate pull request creation from git diffs?▼

Automated pull request creation analyzes git diffs and commit logs against a base branch to generate PR titles and descriptions. It automatically excludes lockfiles to ensure cleaner code reviews and standardized documentation.

Can I synchronize pull requests automatically when pushing new commits?▼

Yes, pull request synchronization automatically detects existing PRs and updates them in-place when new commits are pushed. This prevents duplicate pull requests and maintains a single source of truth for branch changes.

What is the best way to enforce testing checklists in pull request descriptions?▼

Enforcing testing checklists in pull request descriptions requires strict verification of results before allowing checkboxes to be marked. The skill generates PR bodies with standardized testing checklists that demand verified results before completion.

Does automated PR generation work with branch naming conventions and banned characters?▼

Automated PR generation applies branch naming conventions and scans for banned characters during creation. It validates branch names and ensures compliance with repository standards before synchronizing with remote repositories.

How do I update an existing pull request without creating duplicates?▼

Updating existing pull requests without duplicates uses in-place synchronization to detect current PRs and push updates automatically. The system analyzes new commit logs and diffs to refresh the existing PR body and title.

Why should I automate pull request documentation instead of writing it manually?▼

Automating pull request documentation eliminates manual overhead and inconsistency by deriving titles and bodies directly from actual code changes. This ensures PRs accurately reflect modifications rather than relying solely on developer intent.