lukenguyen-me/skills · Archived

commit-message

Generate two conventional commit message options from staged changes and recent commit history.

First seen Jun 6, 2026

Installation

$ npx skills add lukenguyen-me/skills --skill commit-message

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from lukenguyen-me/skills.

npx skills add lukenguyen-me/skills

Browse all from lukenguyen-me/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,346 B
  • docs SUMMARY.md 117 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Generate a new commit message

Check my staged changes only and create a new commit message for it on that, don't add more changes, don't make new commit.

Steps

Check all the staged changes, don't need to check unstaged changes, stop and alert me if there is:

  • Expose of secret key, api key,... all the potential leak of credentials.
  • Log inteded for debugging purposes, not for tracking errors.

Check recent commit history to understand the context of the project.

Create two commit message options based on the staged changes and recent commit history, following conventional commit format.

Option 1 should use the existing multi-line format.

Option 2 should be a one-line version that covers all main points shortly.

Rules

Following conventional commit.

Keep commit message clean, use simple words.

Explain what and why, not how. Don't specify detail on each file, changes,... but group them into same topic.

For option 1, break new line for each topic to improve readability.

For option 2, keep everything on one line while still covering the main points briefly.

DO NOT include any Claude or AI information.

DO NOT execute git commit command, just generate the commit message.