Commit

Draft a Conventional Commits message for the staged changes and commit.

PublishedJun 16, 2026

Loading actions...

5 minBeginnerprompt5 files

Skill content

Main instructions and any bundled files for this skill.

markdown

Additional Files (4)

Review the staged changes with git diff --cached and any unstaged changes with git diff.

Then:

Pick the type: feat, fix, docs, refactor, test, chore, build, ci, perf.
Pick the scope (the module): ingestion, retrieval, topics, graph, app, eval.
Write a concise description — imperative mood, no trailing period, ~60 chars.
For a non-trivial change, add a body explaining why (the diff shows what).
Commit: git commit -m "type(scope): description" (use a heredoc for a body).

Rules:

Do NOT add a Co-Authored-By trailer — commits are attributed to the human author only.
One logical change per commit. If more than ~5 files or ~200 lines are staged, suggest splitting into several commits instead.
Examples:
- feat(retrieval): add BM25 index build and search
- fix(graph): skip outlier topic -1 in belongs_to edges

If nothing is staged, run git status and suggest what to stage based on the recent work. After committing, show git log -1 --oneline.

View Original Source

Related Skills

General

PromptBeginner5 minmarkdown

Untitled Skill

193

Jan 12, 2026

General

PromptBeginner5 minmarkdown

Frontend Typescript Linting.mdc

TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...

160

Feb 15, 2026

General

PromptBeginner5 minmarkdown

2. Apply Deepthink Protocol (reason about dependencies

risks

126

Jan 15, 2026