git

Generate semantic commit messages and Pull Request descriptions from Git history.

82|23|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Rune-kit/rune --skill git-rune-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/Rune-kit/rune/tree/main/skills/git
Command: npx skills add https://github.com/Rune-kit/rune --skill git-rune-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines Git operations by enforcing semantic commit conventions, automating Pull Request descriptions, and providing guidance for branch management and conflict resolution, replacing ad-hoc commands with a structured, convention-aware utility.

Core Features & Use Cases

  • Semantic Commits: Automatically generates commit messages following the Conventional Commits specification based on staged changes.
  • PR Generation: Creates comprehensive Pull Request descriptions by analyzing the entire branch history.
  • Branch Naming: Generates descriptive branch names from task descriptions.
  • Changelog Generation: Compiles changelog entries from commit history.
  • Use Case: Ensure all code changes are committed with clear, machine-readable messages, making your project history clean and facilitating automated changelog generation.

Quick Start

Use the git skill to create a semantic commit for your staged changes.

Frequently Asked Questions about git

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

FAQPage Schema
How do I generate semantic commit messages automatically from staged changes?

To generate semantic commit messages, the Skill analyzes your staged Git changes and produces structured output adhering to the Conventional Commits specification, ensuring clear and machine-readable project history.

What is the best way to compile a changelog from commit history?

Compiling a changelog from commit history is achieved by analyzing past commits and compiling structured changelog entries, strictly adhering to the Keep a Changelog standard for consistent version tracking.

Can I automatically create Pull Request descriptions from branch diffs?

Yes, you can create Pull Request descriptions by analyzing the entire branch diff and commit history, which generates comprehensive PR descriptions that accurately document all included code changes.

Do I need specific tools to run Git operations for branch naming and commits?

You need Git, Bash, Glob, and Grep tools installed in your environment to execute these specialized Git operations, including generating descriptive branch names from task descriptions.

Why use Conventional Commits and Keep a Changelog standards for version control?

Using Conventional Commits and Keep a Changelog standards for version control enforces semantic commit conventions and automates changelog generation, replacing ad-hoc commands with structured, convention-aware utility outputs.

Does this approach work with standard branching workflows and conflict resolution?

Yes, it works with standard branching workflows by providing structured guidance for branch management and conflict resolution, enforcing semantic commit conventions across your version control process.