git-workflow-pr-writing

Write conventional commit messages, PR descriptions, and release notes.

Updated Mar 5, 2026

Search Tags:#git #changelog #commit #pull-request #conventional-commits #gitflow

Ready to run

npx skills add https://github.com/Astrumon/Spovishun --skill git-workflow-pr-writing

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers communicate code changes clearly and maintain a clean, navigable project history by providing consistent commit messages, structured PR descriptions, and guidance for release notes and branch naming.

Core Features & Use Cases

Conventional commit formatting guidance for concise, imperative subjects and explanatory bodies.
Pull request description templates and examples to summarize changes, testing, and related issues.
Branching strategy recommendations following GitFlow and branch naming conventions for features, fixes, and releases.
Merge conflict resolution guidance and example commit messages to record conflict resolution intent and retain context.

Quick Start

Create a conventional-commit style subject and body plus a PR description using the project's template for adding a /ping command that tags a group.

Frequently Asked Questions about git-workflow-pr-writing

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

FAQPage Schema

How do I write conventional commit messages for git pull requests?▼

Conventional commit messages use an imperative subject and an explanatory body to clearly communicate code changes. This format structures git history and pairs with pull request description templates to summarize changes and related issues.

What is the best way to structure pull request descriptions for feature branches?▼

The best way to structure pull request descriptions is using a template that summarizes code changes, testing steps, and related issues. This ensures feature branches maintain clear context and navigable history before merging.

How does GitFlow branch naming work for features and releases?▼

GitFlow branch naming works by applying specific prefixes to differentiate features, fixes, and releases. This organizes repository workflows by clearly identifying branch intent, which helps teams navigate project history during development.

Can I automate changelog drafting from conventional commits?▼

You can automate changelog drafting by leveraging the structured format of conventional commits. Consistent commit subjects and bodies provide the necessary semantic context to generate clear, navigable release notes automatically.

How do I write commit messages for merge conflict resolution?▼

To write commit messages for merge conflict resolution, document the resolution intent and retain original context in the commit body. This records why specific conflicts were resolved in a particular way during feature development.

Do I need co-author attribution lines for AI-assisted commits?▼

You need co-author attribution lines for AI-assisted commits to properly credit tool contributions. Adding these lines to the commit body maintains transparency and accurate authorship history within the project repository.