git

Generate conventional commit messages and update changelogs from repository state.

Updated Jul 5, 2025
One-click install
npx skills add https://github.com/sqfzy/my_configs --skill git-sqfzy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/sqfzy/my_configs/tree/main/claude/skills/git
Command: npx skills add https://github.com/sqfzy/my_configs --skill git-sqfzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates repetitive Git tasks to generate consistent commit messages, write changelogs, and draft PR descriptions based on repository state.

Core Features & Use Cases

  • Generate conventional commit messages aligned with Conventional Commits.
  • Update changelog entries automatically from commits and changes.
  • Optionally draft a PR description to accompany submissions.
  • Auto-detect repo state to determine necessary actions (stage, commit, push).
  • Avoid interfering with other workflows and respect user-defined boundaries.

Quick Start

Tell this skill to stage changes, generate a conventional commit message, and update the changelog for your current branch.

Frequently Asked Questions about git

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

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

Conventional commit messages are generated by auto-detecting your repository state and proposing structured scopes based on the staged changes. This ensures commits align with Conventional Commits standards without manual formatting.

How do I automate changelog updates from recent git commits?

Changelog entries are updated automatically by parsing recent commits and current changes. The changelog reflects conventional commit history, maintaining a consistent log of modifications across your software project branches.

Can I draft PR descriptions automatically from my git branch changes?

PR descriptions are drafted automatically based on your branch's repository state and commit history. This prepares structured submission summaries to accompany your pull requests without manual writing.

Does this git workflow automation auto-detect repository state to stage and push?

Repository state is auto-detected to determine necessary actions including staging, committing, and optionally pushing changes. It respects user-defined boundaries to avoid interfering with other existing workflows.

What is the best way to enforce Conventional Commits across my software project?

Enforcing Conventional Commits is achieved by automating the commit message generation process. The workflow proposes commit scopes and formats messages according to the specification for typical software projects.

When should I avoid using automated git workflow tools?

You should avoid automated git workflow tools when your project requires highly customized commit message structures outside Conventional Commits, or when you need strict manual control over staging and pushing changes.