Generate conventional git commit messages with integrated GitLeaks secret scanning.
npx skills add https://github.com/tartinerlabs/skills --skill commit-tartinerlabs
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
Commit hygiene and security awareness for teams by ensuring every change is recorded as a clean, conventional commit and scanned for secrets.
Stage changes, then run the commit workflow to produce a clean, conventional message and scan with GitLeaks.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
edfentonAutomate local Git hook installation and enforcement for pre-commit checks.
mvandermeulenGenerate project changelogs and release notes from Conventional Commits history.
rohunjDetect hardcoded secrets in repositories with Gitleaks scans.
ruchernchongAutomate GitLeaks secret detection in Husky pre-commit workflows.
