Enforce conventional commit formatting and branch checks before git add and commit.
npx skills add https://github.com/promptlylabs/skills --skill commit-promptlylabs
Please help me install this Agent Skill. Skill: commit Source: https://github.com/promptlylabs/skills/tree/main/plugins/promptly-skills/skills/commit Command: npx skills add https://github.com/promptlylabs/skills --skill commit-promptlylabs
Ensures that code changes are committed with discipline, preventing risky direct commits to protected branches and enforcing conventional commit formatting.
Use this skill to ensure a safe, conventional-commit compliant workflow when committing changes, including branch checks, staged changes review, and properly formatted messages.
High-intent search queries and answers about installing and using this skill.
To enforce conventional commits in your git workflow, this Skill automates type(scope): description syntax validation, reviews staged changes, and blocks commits to protected branches. It ensures formatting discipline and prevents sensitive files from being committed.
The best way to prevent accidental commits to main or master branches is using automated branch discipline. This Skill checks your current branch, prompts feature-branch creation if you are on a protected branch, and validates branch state before allowing any git commit operations to proceed.
Yes, you can block sensitive files like .env from being committed in git. This Skill examines git status and staged changes before committing, automatically detecting and preventing the inclusion of sensitive files, credentials, and unrelated changes to maintain repository security.
To add Co-Authored-By attribution to your conventional commit messages, this Skill provides optional formatting guidelines during the commit workflow. It automatically applies the attribution alongside the required type(scope): description syntax and body guidelines during the git commit operation.
This automated commit workflow works for both solo developers and teams. It scales across Git workflows requiring feature-branch discipline, staged changes review, and conventional commit formatting, making it suitable for maintaining code quality in any software project size or team structure.
Utchash007Stage git changes and generate conventional commit messages with confirmation.
bdsqqqStage modified files, commit with conventional commits, and push to the remote repository.
kirvinRun project-specific linters, formatters, and type checkers on staged files.
mmartinsolivCreate atomic conventional Git commits from staged and unstaged changes.
