git-change-publication

Inspect repository state and draft Conventional Commit messages and PR/MR bodies.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ririnto/sinon --skill git-change-publication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-change-publication
Source: https://github.com/ririnto/sinon/tree/main/plugins/git-workflow/skills/git-change-publication
Command: npx skills add https://github.com/ririnto/sinon --skill git-change-publication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn real repository state into a publishable change narrative by inspecting the working tree, deciding commit readiness, drafting Conventional Commit messages, and assembling hosted PR/MR bodies that respect repository templates for GitHub and GitLab.

Core Features & Use Cases

  • Decide whether staged changes constitute a single logical commit or should be split.
  • Draft a Conventional Commit message from the actual diff with optional scope.
  • Prepare hosted PR/MR bodies that preserve repository templates for GitHub and GitLab.
  • Detect repository host and apply the appropriate template mechanics, with a fallback to SKILL.md guidance when templates are unavailable.

Quick Start

Describe the current repo state to generate a ready-to-publish commit and PR body.

Frequently Asked Questions about git-change-publication

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

FAQPage Schema
How do I draft a Conventional Commit message from a git diff?

To draft a Conventional Commit message from a git diff, the Skill inspects the actual working tree changes and generates a formatted commit message with an optional scope based on the real repository state.

How do I know if my staged changes should be a single commit or split?

Deciding commit readiness involves analyzing the real repository state to determine whether staged changes constitute a single logical commit or should be split into multiple commits.

Can I automatically generate pull request bodies that preserve repository templates for GitHub and GitLab?

Yes, you can generate pull request bodies that preserve repository templates for GitHub and GitLab by detecting the repository host and applying the appropriate template mechanics during drafting.

Does git commit generation work when repository templates are missing?

Git commit generation works when repository templates are missing by falling back to SKILL.md guidance to prepare hosted PR and MR bodies instead of relying on unavailable templates.

What is the best way to prepare a publishable change narrative from a working tree?

The best way to prepare a publishable change narrative from a working tree is to inspect the repository state, decide commit readiness, and assemble hosted PR or MR bodies that respect existing templates.