skills.rest
LibPDF-js
LibPDF-jsOFFICIAL
Explore all skills by this author →
Website𝕏@documensoGitHub

conventional-commit

Generate Conventional Commits messages from staged git changes.

1.8k|62|Updated Jan 11, 2026
Search Tags:#automation#git#workflow#version-control#commit-message#conventional-commits
One-click install
npx skills add https://github.com/LibPDF-js/core --skill conventional-commit-libpdf-js
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/LibPDF-js/core/tree/main/.opencode/skills/conventional-commit
Command: npx skills add https://github.com/LibPDF-js/core --skill conventional-commit-libpdf-js

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes commit messages across a project to improve traceability, reviewing efficiency, and release notes generation.

Core Features & Use Cases

  • Enforces Conventional Commits standards with every commit.
  • Analyzes staged changes and suggests the appropriate type (feat, fix, docs, style, refactor, perf, test, build, ci, chore).
  • Generates subject lines and optional body content, with guidance on scope and breaking changes.
  • Improves changelogs and release note quality by providing structured messages.

Quick Start

Stage your changes with git add, then run the conventional-commit workflow to generate a compliant message for the current changes.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema
How do I automate git commit messages using the Conventional Commits standard?▼

To automate git commit messages, stage your changes and run the workflow to analyze the diff. It determines the appropriate type, generates a compliant subject and body, and prompts for optional scope and breaking changes.

What is the Conventional Commits standard and why use it for git workflow?▼

The Conventional Commits standard structures git commit messages with types like feat, fix, or chore. Using it improves project traceability, reviewing efficiency, and automates release notes generation.

How do I generate a commit type like feat or fix from staged git changes?▼

You can generate the correct commit type by running the workflow after staging changes. It analyzes the diff and automatically suggests a type such as feat, fix, docs, refactor, or chore based on the modifications.

Can I specify a scope or breaking changes in my automated commit messages?▼

Yes, the workflow supports specifying scope and breaking changes. After analyzing your staged changes, it prompts for optional scope and breaking change details to ensure the generated commit message conforms to guidelines.

Do I need any external dependencies to enforce Conventional Commits in my version-control workflow?▼

No external dependencies are required. The workflow operates directly within your version-control workflow to analyze staged changes and generate compliant commit messages without needing additional tools.

What is the best way to improve changelog quality through commit messages?▼

The best way to improve changelog quality is to enforce Conventional Commits standards. Structuring messages with types like feat and fix provides the necessary structured data for generating accurate changelogs and release notes.

Related Skills

Explore More Software Engineering Skills→
74nu574nu5

git-commit

Generate conventional commit messages from diffs and stage files.

Community
Intermediate
dhruvinrsonidhruvinrsoni

release-notes

Parse git history to generate changelogs and release notes.

Community
Advanced
0xjc65eth0xjc65eth
4

git-ops

Standardize Git commits, branching, pre-merge checks, and deployments for CYPHER V3.

Community
Intermediate
daodaoedudaodaoedu

pre-commit-check

Run make check and make lint, then auto-fix with make format.

Official
Intermediate