Run any Skill in Manus with one click

dotfiles-git-commit

Stars2

Forks0

UpdatedJuly 10, 2026 at 19:46

Write and review Git commit messages for the dotfiles repository. Use when drafting a commit message, creating a commit, or checking whether commit text follows this repository's area-prefixed style.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jclem

jclem/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	dotfiles-git-commit
description	Write and review Git commit messages for the dotfiles repository. Use when drafting a commit message, creating a commit, or checking whether commit text follows this repository's area-prefixed style.

Dotfiles Git Commits

Inspect the changes and identify the configuration areas they affect.

Format the subject as <areas>: <imperative statement>:

Use a short lowercase area name such as fish or vim.
Use repo for changes related to this repository itself, such as repository metadata or agent configuration.
Join multiple areas with commas and no spaces.
Sort multiple areas alphabetically.
Write one imperative statement after the prefix.
Capitalise the first word of the statement.
Omit final punctuation.

Examples:

fish: Add vi settings to shell config
fish,vim: Align editor key bindings
repo: Add repository commit conventions
fish,repo: Document Fish configuration conventions

Omit a body for simple changes. When extra context is genuinely useful, add a blank line after the subject followed by one or two short, freeform paragraphs explaining the change.

More from this repository

same repository

add-lsp-configs

jclem/dotfiles

Add or update Neovim 0.12 language-server configurations using native vim.lsp APIs, nvim-lspconfig defaults, vim.pack, and Mise-managed server executables. Use when adding a language server, migrating an LSP spec, changing server settings, enabling LSP formatting, or validating LSP behavior in the dotfiles Neovim configuration.

2026-07-102

add-neovim-plugins

jclem/dotfiles

Add, configure, update, or remove Neovim 0.12 plugins in the dotfiles repository using the native vim.pack package manager. Use when introducing a plugin, replacing a plugin, adding plugin dependencies or build hooks, configuring native plugin loading, or maintaining the Neovim package lockfile.

2026-07-102

write-fish-functions

jclem/dotfiles

Create, rewrite, and review Fish functions for the dotfiles repository using its standard file layout, documentation, argument parsing, long-form options, error handling, safety checks, and validation. Use whenever adding or modifying a file under dot_config/fish/functions.

2026-07-102

name	dotfiles-git-commit
description	Write and review Git commit messages for the dotfiles repository. Use when drafting a commit message, creating a commit, or checking whether commit text follows this repository's area-prefixed style.

Dotfiles Git Commits

Inspect the changes and identify the configuration areas they affect.

Format the subject as <areas>: <imperative statement>:

Use a short lowercase area name such as fish or vim.
Use repo for changes related to this repository itself, such as repository metadata or agent configuration.
Join multiple areas with commas and no spaces.
Sort multiple areas alphabetically.
Write one imperative statement after the prefix.
Capitalise the first word of the statement.
Omit final punctuation.

Examples:

fish: Add vi settings to shell config
fish,vim: Align editor key bindings
repo: Add repository commit conventions
fish,repo: Document Fish configuration conventions

Omit a body for simple changes. When extra context is genuinely useful, add a blank line after the subject followed by one or two short, freeform paragraphs explaining the change.