commit

Generate conventional git commit messages with integrated GitLeaks secret scanning.

7|1|Updated Feb 14, 2026

Search Tags:#git #workflow #commit #pre-commit #conventional-commit #lint-staged #gitleaks

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit hygiene and security awareness for teams by ensuring every change is recorded as a clean, conventional commit and scanned for secrets.

Core Features & Use Cases

Enforces conventional commit messages with optional GitLeaks scanning for the repository.
Helps maintain changelog quality and traceability across releases.
Use case: when preparing a release, ensure all changes are committed in a single-commit style and secrets are not leaked.

Quick Start

Stage changes, then run the commit workflow to produce a clean, conventional message and scan with GitLeaks.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automate conventional commit messages and prevent secret leaks?▼

To automate conventional commit messages and prevent secret leaks, you can use a workflow that generates well-formed commits and scans staged changes with GitLeaks before finalizing the commit. This ensures messages are auditable and secrets are not leaked.

What is the best way to enforce conventional commit formatting for release preparation?▼

Enforcing conventional commit formatting for release preparation involves applying a standardized workflow that generates clean, single-commit style messages. This maintains changelog quality and traceability across releases by ensuring every change is well-formed and auditable.

How does GitLeaks scanning integrate with conventional commits?▼

GitLeaks scanning integrates with conventional commits by scanning the repository during the commit workflow. This combined mechanism ensures that while commit messages are being automatically formatted to conventional standards, the changes are simultaneously checked for exposed secrets.

Do I need pre-commit hooks to scan for secrets and format commits?▼

Using pre-commit hooks to scan for secrets and format commits is a standard approach for secure development workflows. This Skill applies to standard development processes by ensuring changes are recorded as clean commits and scanned with GitLeaks before finalizing.

Can I use lint-staged with conventional commits and GitLeaks scanning?▼

Yes, you can use lint-staged with conventional commits and GitLeaks scanning as part of a secure development workflow. The workflow applies to standard development processes, ensuring feature work and bug fixes are well-formed and auditable.

When should I not use an automated conventional commit workflow?▼

You should not use an automated conventional commit workflow if your project does not require strict commit hygiene or changelog traceability. It is specifically designed for teams adopting conventional commits and secret detection as part of a structured release preparation process.