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.

Copilot ✓Cursor ✓Kilo ✓
AuthorNeexoCore
Sourcegithub.com/NeexoCore/awesome-neexo
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.
Download ZIP
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

This skill is for repositories where a commit is not just a message but a final quality gate. It covers both quick conventional commit message generation and the fuller review workflow for higher-risk changes.

Workflow

  1. Inspect changes — read staged and unstaged diffs with git diff --cached and git diff
  2. Check recent history — run git log --oneline -10 to match existing commit style
  3. Verify generated files — ensure schema changes include their migration SQL, lock files are updated, build output is excluded
  4. Check changelog date — if a changelog entry is staged, verify the date is correct (run node -e "console.log(new Date().toISOString().slice(0,10))")
  5. Produce message — write a conventional commit message that matches the repository's style

Message Rules

  • Use conventional commit format: type(scope): subject
  • Valid types: feat, fix, docs, style, refactor, test, chore, perf, ci, build
  • Keep subject lines under 72 characters, imperative mood, with no trailing period
  • Prefer outcome over implementation detail: fix: prevent duplicate order emails rather than fix: add check in sendEmail function

Quality Gates

  • Schema changes, generated migrations, and dependent code must be in the same commit
  • Non-English changelog or release notes must use correct locale characters — never ASCII substitutes for accented letters
  • Never set featured: true without justification
  • Do not commit .env files, secrets, or large binary assets

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

This skill is for repositories where a commit is not just a message but a final quality gate. It covers both quick conventional commit message generation and the fuller review workflow for higher-risk changes.

## Workflow

1. **Inspect changes** — read staged and unstaged diffs with `git diff --cached` and `git diff`
2. **Check recent history** — run `git log --oneline -10` to match existing commit style
3. **Verify generated files** — ensure schema changes include their migration SQL, lock files are updated, build output is excluded
4. **Check changelog date** — if a changelog entry is staged, verify the date is correct (run `node -e "console.log(new Date().toISOString().slice(0,10))"`)
5. **Produce message** — write a conventional commit message that matches the repository's style

## Message Rules

- Use conventional commit format: `type(scope): subject`
- Valid types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`, `perf`, `ci`, `build`
- Keep subject lines under 72 characters, imperative mood, with no trailing period
- Prefer outcome over implementation detail: `fix: prevent duplicate order emails` rather than `fix: add check in sendEmail function`

## Quality Gates

- Schema changes, generated migrations, and dependent code **must** be in the same commit
- Non-English changelog or release notes must use correct locale characters — never ASCII substitutes for accented letters
- Never set `featured: true` without justification
- Do not commit `.env` files, secrets, or large binary assets

## 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

Copy install prompt

One prompt — your agent fetches and writes the skill folder.

Jump to install

Browse all skills

Every bundled skill uses the same one-prompt flow.

View skills

Related resources

Figma-to-Code Workflow

Step-by-step recipe for turning Figma designs into production code using the official Figma MCP server, Code Connect, and AI agent rules.

Copilot ✓Cursor ✓Kilo ✓
figmadesign-to-codeworkflow

Fetch Neexo Hub Context★

Load stack-specific conventions from awesome.neexo.dk without dumping the full catalog.

Copilot ✓Cursor ✓Kilo ✓
hubcontextplaybooks

Agent Session Diary

Maintain a lightweight decision log across agent sessions for handoff and auditability.

Copilot ✓Cursor ✓Kilo ✓
diaryhandoffdocumentation

Blender Render Pipeline

Headless Blender rendering via subprocess queues with idempotent job handling.

Copilot ✓Cursor ✓Kilo ✓
blenderrendering

Matched by shared tags and category. Browse all cookbook