commit

Create safe conventional git commits from staged changes.

Updated Apr 25, 2026

Search Tags:#git #commit #staging #version-control #conventional-commits #secrets-scanning

Ready to run

npx skills add https://github.com/lukeylias/lukeydev --skill commit-lukeylias

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/lukeylias/lukeydev/tree/main/skills/commit
Command: npx skills add https://github.com/lukeylias/lukeydev --skill commit-lukeylias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create safe, clean git commits without accidentally bundling unrelated changes or exposing sensitive data.

Core Features & Use Cases

Reviews repository state before committing so you can see staged and unstaged changes clearly.
Scans for secrets and blocks risky commits when it detects API keys, private keys, or suspicious credentials-like content.
Checks .gitignore coverage, encourages logical grouping of changes, and uses conventional commit messages for readable history.
Useful when you need to turn a messy working tree into one or more disciplined commits with minimal risk.

Quick Start

Ask the AI to inspect the current git changes and help you prepare a safe conventional commit for only the files that should be included.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I scan staged git changes for secrets before committing?▼

To scan for secrets before a git commit, you need a process that inspects git diff output for API keys, private keys, and suspicious credentials-like content, blocking risky commits when sensitive data is detected.

What is the best way to format conventional commit messages from existing staged changes?▼

The best way to format conventional commit messages is to inspect staged git changes, separate logical modifications, and generate a structured commit message that ensures a readable and clean version-control history.

How do I separate logical changes in a messy working tree into disciplined git commits?▼

To separate logical changes in a messy working tree, review the repository status to distinguish staged and unstaged files, validate .gitignore coverage, and selectively stage related modifications into isolated commits.

Can I validate my .gitignore coverage and avoid accidental inclusion of untracked files when committing?▼

Yes, you can validate .gitignore coverage during the staging process by reviewing git status, checking that untracked files are properly ignored, and selectively staging only the intended modifications.

Does git commit workflow automation require lint or test confirmation before staging changes?▼

A disciplined git commit workflow often requires lint or test confirmation prior to finalizing the commit, ensuring that the selectively staged changes pass validation and maintain repository stability.