skills.rest
dangvu008
dangvu008COMMUNITY
Explore all skills by this author →
GitHub

rune-git

Generates semantic commits, PR descriptions, branch names, and changelogs from git diffs.

1|Updated Mar 22, 2026
Search Tags:#git#changelog#pull request#conventional commits#github#branch naming#release tagging
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-git-dangvu008
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rune-git
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-git
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-git-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent commit messages, PR descriptions, and changelogs by hand is repetitive and error-prone, often leading to vague history, missed breaking changes, and inconsistent conventions across a team. ## Core Features & Use Cases - Semantic Commits: Analyzes staged diffs to classify change type (feat, fix, refactor, etc.), detect scope, and generate conventional commit messages with breaking-change footers. - PR & Branch Management: Reads all commits on a branch to produce complete PR descriptions with summaries and test plans, and generates kebab-case branch names from task descriptions. - Changelog & Release: Groups commits since the last tag into Keep a Changelog format, bumps versions, creates tags, and publishes GitHub Releases. - Use Case: After finishing a feature, stage your changes and ask for a commit — the skill reads the full diff, detects a breaking API change, and produces feat(auth)!: add JWT refresh token rotation with a proper BREAKING CHANGE footer. ## Quick Start Ask the assistant to create a semantic commit for your currently staged changes using the rune-git skill.

Frequently Asked Questions about rune-git

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

FAQPage Schema
How do I generate a conventional commit message automatically?▼

Stage your changes, then invoke the commit mode. It reads the full staged diff, classifies the change type (feat, fix, refactor, docs, etc.), extracts scope from file paths, and produces a conventional commit message with a breaking-change footer when needed.

How to write a pull request description covering all branch commits?▼

PR mode reads every commit on the branch using git log and git diff against the base branch, not just the latest one. It then generates a summary, grouped changes, a test plan, and breaking-change notes, and creates the PR with gh pr create.

Does it detect breaking changes in commits?▼

Yes. It flags breaking changes by checking for removed exports, changed function signatures, and schema modifications. Detected breaking changes get a ! suffix on the commit type and a BREAKING CHANGE footer in the message body.

Can I generate a changelog from git commit history?▼

Yes. Changelog mode reads commits since the last tag, groups them by conventional commit type, and formats them following the Keep a Changelog standard with Added, Fixed, Changed, and Removed sections linked to PRs.

What happens if pre-commit hooks fail during commit?▼

The skill reports the hook failure and stops rather than bypassing it. It never uses --no-verify, so you must fix the underlying issue before the commit can be completed.

Related Skills

Explore More Software Engineering Skills→
OpenAuthorityOpenAuthority
8

git_status

Report staged, unstaged, and untracked files from git status --porcelain.

Official
Intermediate
tribedotruntribedotrun
8

mando-pr

Create GitHub pull requests and trigger AI reviewers with CI monitoring.

Official
Advanced
DataDogDataDog
648

lint

Run Hatch-based lint, format, and quality checks on modified files.

Official
Advanced
JiangAustinJiangAustin

chinese-commit-conventions

Standardize Chinese Git commit messages with commitlint, husky, and commitizen.

Community
Intermediate