Conventional Commit

Organization

navikt

conventional-commit

Generer conventional commit-meldinger med Nav-relevante scopes og breaking change-format

Overview

Publisher	navikt
Repository	`copilot`
Skill name	`conventional-commit`
Stars	60
Forks	16
Bundled files	1
License	MIT
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.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by navikt on GitHub. Read the source before you install it.

Installation

Install the Conventional Commit 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.
https://github.com/navikt/copilot/tree/main/skills/conventional-commit
Enable the skill in any chat where you want it available.

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/navikt/copilot.git /tmp/copilot
mkdir -p .claude/skills
cp -r /tmp/copilot/skills/conventional-commit .claude/skills/conventional-commit

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

Use it in TypingMind

Enable Conventional Commit 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 Conventional Commit 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 Conventional Commit 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 Commit Skill

Generate commit messages following the Conventional Commits specification, adapted for Nav projects.

Format


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

[optional body]

[optional footer]

Types

Type	Usage
`feat`	New functionality
`fix`	Bug fix
`docs`	Documentation-only changes
`style`	Formatting, semicolons, etc. (no code change)
`refactor`	Code that neither fixes a bug nor adds a feature
`perf`	Performance changes
`test`	Adding or fixing tests
`build`	Build system or dependency changes
`ci`	CI configuration changes
`chore`	Other changes that don't affect code

Nav-relevant scopes


feat(vedtak): add support for complaint decisions
fix(auth): fix token validation for TokenX
docs(api): update OpenAPI spec for the vedtak endpoint
refactor(repository): use CTE for better readability
test(controller): add integration test with MockOAuth2Server
build(deps): upgrade Spring Boot to 3.4.1
ci(deploy): add prod deploy step
perf(db): add index on bruker_id
chore(nais): update resource limits

Breaking Changes


feat(api)!: change response format for the vedtak endpoint

BREAKING CHANGE: The `vedtakDato` field has been changed to `opprettetDato`.
Consumers must update their parsing.

Rules

First line: max 72 characters
Use imperative form: "add", not "added" or "adds"
Don't end with a period
Use Norwegian or English consistently within the project
Reference Jira/GitHub issue in footer: Closes #123 or Refs NAV-1234

Examples

bash
# Simple feature
git commit -m "feat(søknad): add validation of national identity number"

# Bugfix with reference
git commit -m "fix(auth): handle expired refresh token

The refresh token was not renewed upon expiration, which caused
users to be logged out without warning.

Fixes #456"

# Dependency update
git commit -m "build(deps): upgrade postgresql driver to 42.7.4"

# Breaking change
git commit -m "feat(api)!: remove deprecated /api/v1/vedtak endpoint

BREAKING CHANGE: /api/v1/vedtak has been removed. Use /api/v2/vedtak."

Analyzing Staged Changes

To generate a commit message, analyze staged changes:

bash
git diff --cached --stat        # Overview of changed files
git diff --cached               # Detailed diff

Based on the diff:

Identify type (feat/fix/refactor/etc.)
Identify scope (which module/domain)
Write short, precise description
Add body if the change needs explanation
Add BREAKING CHANGE footer if the API changes

Bundled files

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

metadata.json1 KB

Frequently asked questions

What does the Conventional Commit AI skill do?

Generer conventional commit-meldinger med Nav-relevante scopes og breaking change-format

Why use Conventional Commit on TypingMind?

Because you install it once and use it with any model. Conventional Commit 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 Conventional Commit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/navikt/copilot/tree/main/skills/conventional-commit. 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 Conventional Commit?

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 Conventional Commit?

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

Is the Conventional Commit AI skill free?

Yes. It is published on GitHub by navikt under the MIT license. 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

Auto Qa

openclaw

OrganizationPopular

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Clawsweeper

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Conventional Commit Skill

Format

Types

Nav-relevant scopes

Breaking Changes

Rules

Examples

Analyzing Staged Changes

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now