Skip to content
cccskills
FreePublished on GitHub

git-commit-helper

Write clear, conventional git commit messages from staged changes. Use when the user asks to commit work, write a commit message, or clean up a commit history.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Git Commit Helper

Produce a well-formed commit message from the currently staged diff.

Workflow

  1. Run git diff --staged to see what is actually being committed. If nothing is staged, tell the user and stop — do not stage files yourself.
  2. Run git log --oneline -10 to match the repository's existing message style (conventional commits vs. plain sentences).
  3. Draft the message:
    • Subject line: imperative mood, under 72 characters, no trailing period.
    • Body: explain why the change was made, not a list of what files changed.
    • If the repo uses conventional commits, pick the correct type (feat, fix, refactor, docs, test, chore).
  4. Show the draft to the user before committing.

Rules

  • One logical change per commit. If the staged diff mixes unrelated changes, point that out and suggest splitting instead of committing anyway.
  • Never use --amend or force-push unless the user explicitly asks.
  • Do not invent ticket numbers or issue references.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Diagnose failing HTTP API calls - 4xx/5xx responses, timeouts, TLS errors, and auth failures - by isolating the fault layer and producing a minimal reproduction. Use when the user reports an API request failing, pastes an HTTP error response or status code, or asks why a request works in one client but not another. Do not use for designing new APIs or for performance tuning of requests that already succeed.

The English summary is being prepared. Showing the original description.

Krusty84/SKILL.md-Inspector43Updated Aug 1, 2026

Reduce a failing test case, script, or input file to the smallest version that still reproduces a bug. Use when the user has a large reproduction and asks to minimize, bisect, or isolate it, or says things like "it stops failing when I remove half the file". Do not use when there is no reliable reproduction yet - help build one first, then minimize it.

The English summary is being prepared. Showing the original description.

Krusty84/SKILL.md-Inspector43Updated Aug 1, 2026

Generate or update a CHANGELOG.md from merged commits and pull requests, grouped by change type and written for end users. Use when the user asks to write release notes, update the changelog, or summarize what changed between two versions or tags. Do not use for writing individual commit messages or for API-reference documentation.

The English summary is being prepared. Showing the original description.

Krusty84/SKILL.md-Inspector43Updated Aug 1, 2026

Apply the team style guide to source files - naming conventions, comment style, and file organization. Use when the user asks to align code with the style guide or clean up naming.

The English summary is being prepared. Showing the original description.

Krusty84/SKILL.md-Inspector43Updated Aug 1, 2026

Run the project's configured formatter (prettier, black, gofmt, rustfmt) on changed files and fix formatting-only CI failures. Use when the user asks to format code, fix a lint/format CI step, or normalize whitespace and import order. Do not use for logic changes or refactoring.

The English summary is being prepared. Showing the original description.

Krusty84/SKILL.md-Inspector43Updated Aug 1, 2026

Clean and normalize messy CSV/TSV files - fix malformed rows, inconsistent headers, mixed encodings, stray delimiters, and duplicated records - and deliver a valid, verified file. Use when the user mentions a broken, messy, or malformed CSV, a file a spreadsheet tool refuses to open, or asks to deduplicate or normalize tabular data. Do not use when the deliverable is analysis or a chart rather than a cleaned file, or for Excel-native features like formulas and pivot tables.

The English summary is being prepared. Showing the original description.

Krusty84/SKILL.md-Inspector43Updated Aug 1, 2026

See all skills by Krusty84

Report a problem with this skill