skills.rest
Pieter-1337
Pieter-1337COMMUNITY
Explore all skills by this author →
GitHub

commit

Creates git commits following Conventional Commits with secret scanning and changelog updates.

Updated May 7, 2026
Search Tags:#git#changelog#version control#commit#conventional commits#secret detection
One-click install
npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill commit-pieter-1337
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Pieter-1337/Euricom-tsz/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill commit-pieter-1337

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It standardizes how changes are committed in a repository by enforcing a consistent commit message format, preventing accidental commits of secrets, and keeping the changelog up to date automatically. ## Core Features & Use Cases - Conventional Commits Enforcement: Generates commit messages with flat types (feat, fix, docs, refactor, etc.), imperative mood, and a 72-character subject limit. - Secret Detection: Scans filenames and diff content for credentials, API keys, tokens, and .env files before staging anything. - Automatic Changelog Updates: Appends each commit message to CHANGELOG.md under the current date heading. - Use Case: After finishing a bug fix, ask the assistant to commit; it inspects git status and diff, checks for secrets, writes a properly formatted message like "fix: handle null user session", and logs it to the changelog without pushing. ## Quick Start Ask the assistant to commit the current changes in the repository.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a Conventional Commits message?▼

Use the format "<type>: <subject>" with a flat type like feat, fix, docs, refactor, or chore, and no scope. Write the subject in imperative mood, keep it under 72 characters, and omit the trailing period.

How to check for secrets before committing changes?▼

Scan filenames and diff content for patterns like .env files, credentials, API keys, tokens, and private keys before staging. If anything sensitive appears, stop and confirm with the user before proceeding.

Should multiple unrelated changes go into one commit?▼

Bundle all pending changes into a single commit by default. If the changes clearly span unrelated concerns, ask the user whether to split them into separate commits before proceeding.

Does this commit workflow push changes automatically?▼

No, it never runs git push automatically. Pushing only happens when the user explicitly requests it, such as by saying "push" or "commit and push".

How are commit messages added to the changelog?▼

The commit message is appended verbatim to CHANGELOG.md under a "## YYYY-MM-DD" heading for today's date. If the heading does not exist, a new one is inserted at the top below the "# Changelog" title.

Related Skills

Explore More Software Engineering Skills→
JoeCP17JoeCP17
8

commit

Create conventional git commit messages from working tree changes.

Community
Intermediate
santychuycomsantychuycom

ship

Analyze diffs, create atomic conventional commits, push, and open pull requests.

Official
Advanced
RambleRainbowRambleRainbow

plankton-code-quality

Run formatters and linters on file edits to catch code violations.

Community
Advanced
theslashdojotheslashdojo

git-rebase

Replay commits onto a new base with interactive rebase and autosquash.

Official
Intermediate