omk-git-commit-pr

Generate Conventional Commits messages and pull request summaries from code diffs.

130|14|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-git-commit-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omk-git-commit-pr
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/agents/omk-git-commit-pr
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-git-commit-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a messy code diff into a clear, consistent Git commit message and an evidence-aligned pull request summary, reducing review friction and improving traceability.

Core Features & Use Cases

  • Conventional Commits formatting: Produces commit messages following a scope-based Conventional Commits style (feat, fix, refactor, test, docs, chore).
  • Diff-based grouping and summarization: Inspects the current diff, groups changes by purpose, and excludes unrelated edits so the output stays focused.
  • PR summary generation (when requested): Generates a PR body that separates What changed, Why, Test result, Risk, and Notes while keeping claims factual and evidence-gated.

Use case: After completing a feature branch, you want your commit message(s) and PR description to accurately reflect only the meaningful changes from the diff, without overstating test results or including irrelevant modifications.

Quick Start

Ask the agent to generate a Conventional Commits commit message and a pull request summary based on the current diff, ensuring all statements are evidence-backed and any missing tests are clearly reported.

Frequently Asked Questions about omk-git-commit-pr

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

FAQPage Schema
How do I generate a conventional commit message from a git diff?

To generate a conventional commit message from a git diff, the Skill inspects the current code changes, groups them by purpose, and applies Conventional Commits formatting using scopes like feat, fix, or refactor.

How do I write a pull request summary from my current code changes?

You can write a pull request summary from your current code changes by transforming the diff into a structured PR body that clearly separates What changed, Why, Test result, Risk, and Notes.

How do I ensure my PR descriptions do not falsely claim tests passed?

To ensure your PR descriptions do not falsely claim tests passed, the Skill enforces evidence-aligned documentation by gating factual claims and only asserting test results if they were actually run.

Can I exclude unrelated edits from my git commit messages and PR summaries?

Yes, you can exclude unrelated edits from your commit messages and PR summaries because the diff analysis groups changes by purpose while filtering out irrelevant modifications to keep the output focused.

What is the best way to summarize a feature branch for a code review?

The best way to summarize a feature branch for a code review is to generate an evidence-aligned PR summary that accurately reflects meaningful changes from the diff, reducing review friction and improving traceability.

Does this approach work for refactor and maintenance workflows or only new features?

This approach works for refactor and maintenance workflows as well as new features, applying consistent conventional commit formatting and impact summarization across feature, bugfix, and maintenance code changes.