Conventionalcommits

Organization

NeverSight

conventionalcommits

Conventional Commits specification for semantic versioning and changelog generation. Use when writing commit messages, configuring commit linting, or automating releases.

Overview

Publisher	NeverSight
Repository	`learn-skills.dev`
Skill name	`conventionalcommits`
Stars	210
Forks	38
Bundled files	12
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
12 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by NeverSight on GitHub. Read the source before you install it.

Installation

Install the Conventionalcommits AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/0froq/skills/conventionalcommits

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git /tmp/learn-skills.dev
mkdir -p .claude/skills
cp -r /tmp/learn-skills.dev/data/skills-md/0froq/skills/conventionalcommits .claude/skills/conventionalcommits

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Conventionalcommits in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Conventionalcommits on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Conventionalcommits is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Conventional Commits

Based on Conventional Commits v1.0.0. A lightweight convention for writing commit messages that communicates intent and enables automated tooling.

The Conventional Commits specification provides a structured format for commit messages. It supports semantic versioning, changelog generation, and clearer project history.

Core Concepts

Topic	Description	Reference
Structure	Type, scope, description, body, footer format	core-structure
Types	feat, fix, and optional type conventions	core-types
SemVer Mapping	How commits translate to version bumps	core-semver
Format Details	Scopes, bodies, footers, breaking changes	core-format

Quick Reference

Commit Structure


<type>(<scope>): <description>

<body>

<footer>

Types and SemVer

Type	SemVer	Use For
`feat`	MINOR	New features (normative per spec)
`fix`	PATCH	Bug fixes (normative per spec)
`docs`	—	Documentation changes (convention)
`refactor`	—	Code restructuring (convention)
`perf`	—	Performance improvements (convention)
`test`	—	Test additions/changes (convention)
`build`	—	Build system changes (convention)
`ci`	—	CI configuration (convention)
`style`	—	Code style changes (convention)

Note: Only feat, fix, and breaking-change markers have normative SemVer meaning in the specification. Other types are optional conventions—tools may categorize them differently. chore is intentionally excluded from recommendations; use specific types above for clarity.

Breaking Changes


feat(api)!: redesign user authentication

BREAKING CHANGE: auth token format changed from JWT to opaque tokens

Examples

bash
# New feature
feat: add dark mode toggle

# Bug fix with scope
fix(auth): resolve token expiration bug

# Breaking change
feat(api)!: remove deprecated endpoints

# With body and footer
feat(search): implement fuzzy matching

Adds Levenshtein distance algorithm for typo-tolerant search.

Closes #123

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Conventionalcommits AI skill do?

Conventional Commits specification for semantic versioning and changelog generation. Use when writing commit messages, configuring commit linting, or automating releases.

Why use Conventionalcommits on TypingMind?

Because you install it once and use it with any model. Conventionalcommits is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Conventionalcommits in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/0froq/skills/conventionalcommits. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Conventionalcommits?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Conventionalcommits?

As many as you like. As long as a model supports skills, you can use Conventionalcommits with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Conventionalcommits AI skill free?

It is published on GitHub by NeverSight. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Codebase Design

mattpocock

CommunityPopular

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or…

Diagnosing Bugs

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Implement

Implement a piece of work based on a spec or set of tickets.

Improve Codebase Architecture

mattpocock

CommunityPopular

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Conventional Commits

Core Concepts

Quick Reference

Commit Structure

Types and SemVer

Breaking Changes

Examples

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now