git

Generate conventional git commits, branch names, and pull request descriptions.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/linenoize/topia --skill git-linenoize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/linenoize/topia/tree/main/skills/git
Command: npx skills add https://github.com/linenoize/topia --skill git-linenoize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from Git operations by turning scattered commit, branch, pull request, changelog, and release tasks into one consistent workflow with clear conventions and safety checks.

Core Features & Use Cases

  • Semantic commits: Classifies staged changes and produces conventional commit messages with the right type, scope, and breaking-change markers.
  • Pull request generation: Reviews the full branch diff and commit history to create complete PR summaries, change lists, and test plans.
  • Branch naming and releases: Generates kebab-case branch names, changelogs, and semver release tags while respecting existing repository conventions.
  • Use case: A developer finishes a feature, then asks this Skill to inspect the diff, write the commit message, and prepare the release or PR text without manually stitching everything together.

Quick Start

Use the git skill to inspect the staged changes in this repository and generate the correct conventional commit message.

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 from staged git diffs?

To generate conventional commit messages from staged git diffs, the Skill inspects the full staged changes, classifies the modifications, and applies conventional commit rules to produce the correct type, scope, and breaking-change markers automatically.

Can I automatically generate pull request descriptions from branch history?

You can automatically generate pull request descriptions by having the Skill review the full branch diff and commit history, which produces complete PR summaries, structured change lists, and test plans for collaborative workflows.

What is the best way to prepare semver release tags and changelogs from repository changes?

Preparing semver release tags and changelogs from repository changes is best handled by inspecting branch histories and applying semver validation, generating consistent release tags and formatted changelogs that respect existing repository conventions.

Does this git workflow generation respect existing branch naming conventions?

Yes, the git workflow generation respects existing repository conventions by analyzing current branch histories and formatting rules to generate kebab-case branch names that align with your established collaborative GitHub workflows.

How does breaking-change detection work for conventional commits?

Breaking-change detection for conventional commits works by inspecting the full staged diff, identifying modifications that break backward compatibility, and appending the correct breaking-change markers to the generated commit messages.

Are force-pushes or hook bypasses used when generating git commits and release tags?

No, force-pushes and hook bypasses are strictly avoided to ensure safe execution. The Skill applies conventional commit rules and semver validation while maintaining repository integrity during commit, changelog, and release tag generation.