Neexo Git Commit Skill

A full commit workflow skill that inspects diffs, checks repository history, verifies generated files and changelog dates, and produces a commit-ready message.

CopilotCursorKilo
AuthorNeexoCore
Updated
gitcommitchangelogworkflow

Install in your repo

You get: 1 SKILL.md

Copy one prompt into Cursor, Copilot, Kilo, or any agent with web access.

Install the Neexo skill "Neexo Git Commit Skill" (git-commit) in this repository.

Manifest: https://awesome.neexo.dk/api/install-manifest?ids=skills%2Fgit-commit
Catalog: https://awesome.neexo.dk/skills/git-commit

Steps:
1. Fetch https://awesome.neexo.dk/api/install-manifest?ids=skills%2Fgit-commit and read the file list.
2. Fetch https://awesome.neexo.dk/api/skills/git-commit/bundle and write every file to the correct project skill folder.
3. Detect IDE from this repo (.cursor → Cursor, .kilo → Kilo).
4. Preserve subdirectory structure (references/, agents/, scripts/, assets/).
5. Confirm which files you wrote.
Advanced — manual CLI
CLI — Cursor + Kilonpx awesome-neexo install skill git-commit --all
CLI — Cursor onlynpx awesome-neexo install skill git-commit --cursor
Copilot — full plugincopilot plugin install neexo-developer@awesome-neexo
Bundle API (JSON)https://awesome.neexo.dk/api/skills/git-commit/bundle

Overview

Template skill for repositories where a commit is a quality gate. Consuming repos override scopes, validation commands, and changelog locale rules via their own skill copy or AGENTS.md — those win on conflict.

Workflow

  1. Inspect changesgit status --short, git diff --cached, git diff
  2. Check recent historygit log --oneline -10 to match style
  3. Verify generated files — schema + migration SQL together; no build artifacts or secrets
  4. Product changelog — if the repo uses fragment-first changelogs and the change is user-visible, follow the product-changelog skill (catchup → fragment → build → check)
  5. Test gate — follow the test-gate skill (ci:check or documented fallback) before commit
  6. Produce message — conventional commit matching the repository's style

Message Rules

  • Format: type(scope): subject
  • Valid types (adjust if the repo documents others): feat, fix, docs, style, refactor, test, chore, perf, ci, build, schema
  • Subject under 72 characters, imperative mood, no trailing period
  • Prefer outcome over implementation detail

Scopes (override layer)

This hub skill does not own product scopes. Read the consuming repo's commit skill or AGENTS.md for the allowed scope table (examples only: auth, billing, documents, ui, infra).

Quality Gates

  • Schema changes, generated migrations, and dependent code must be in the same commit
  • User-facing changelog copy must use correct locale characters for the product UI language(s)
  • Never commit .env files, secrets, or large binary assets
  • Do not use --no-verify unless the user explicitly requests it

Examples

feat(auth): add MFA support for organization admins
fix(billing): prevent duplicate invoice generation on retry
docs: update Drizzle migration workflow in README
chore(deps): bump next from 16.1.0 to 16.2.6

Raw content

Copy into your project — e.g. .instructions.md, .agent.md, or SKILL.md

## Overview

Template skill for repositories where a commit is a quality gate. **Consuming repos override** scopes, validation commands, and changelog locale rules via their own skill copy or AGENTS.md — those win on conflict.

## Workflow

1. **Inspect changes** — `git status --short`, `git diff --cached`, `git diff`
2. **Check recent history** — `git log --oneline -10` to match style
3. **Verify generated files** — schema + migration SQL together; no build artifacts or secrets
4. **Product changelog** — if the repo uses fragment-first changelogs and the change is user-visible, follow the `product-changelog` skill (catchup → fragment → build → check)
5. **Test gate** — follow the `test-gate` skill (`ci:check` or documented fallback) before commit
6. **Produce message** — conventional commit matching the repository's style

## Message Rules

- Format: `type(scope): subject`
- Valid types (adjust if the repo documents others): `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`, `perf`, `ci`, `build`, `schema`
- Subject under 72 characters, imperative mood, no trailing period
- Prefer outcome over implementation detail

## Scopes (override layer)

This hub skill does **not** own product scopes. Read the consuming repo's commit skill or AGENTS.md for the allowed scope table (examples only: `auth`, `billing`, `documents`, `ui`, `infra`).

## Quality Gates

- Schema changes, generated migrations, and dependent code **must** be in the same commit
- User-facing changelog copy must use correct locale characters for the product UI language(s)
- Never commit `.env` files, secrets, or large binary assets
- Do not use `--no-verify` unless the user explicitly requests it

## Examples

```text
feat(auth): add MFA support for organization admins
fix(billing): prevent duplicate invoice generation on retry
docs: update Drizzle migration workflow in README
chore(deps): bump next from 16.1.0 to 16.2.6
```

Next steps

Matched by shared tags and category. Browse all skills