Create conventional Git commits for staged changes with enforced branch naming.
npx skills add https://github.com/CodySwannGT/lisa --skill git-commit-codyswanngt
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/CodySwannGT/lisa/tree/main/plugins/lisa/skills/git-commit Command: npx skills add https://github.com/CodySwannGT/lisa --skill git-commit-codyswanngt
This Skill streamlines the process of creating conventional commits for your code changes, ensuring consistency and clarity in your version control history.
Use the git-commit skill to create a conventional commit for your current changes.
High-intent search queries and answers about installing and using this skill.
To automate conventional commits, this Skill stages your changes and generates formatted commit messages using types like feat, fix, chore, and docs. It ensures all files are included and verifies the working directory is clean.
The conventional commit format standardizes version control history by prefixing messages with specific types. Supported types include feature, fix, chore, docs, style, refactor, and test, ensuring clarity and consistency across your branching workflow.
Yes, this conventional commit tool enforces branch naming conventions specifically for development and staging branches. It checks branch names before committing to maintain strict version control workflow standards.
To ensure all staged files are included in a git commit, this Skill automates the process by verifying staged changes and generating a complete conventional commit. It prevents lost work by confirming a clean working directory afterwards.
Yes, you can create a chore commit type for routine maintenance. This Skill supports feature, fix, chore, docs, style, refactor, and test commit types to categorize your version control changes accurately.
The best way to maintain a clean working directory after committing is to use an automated conventional commit process. This Skill verifies the working directory is clean post-commit, ensuring no staged files are left behind.
mhattingpeteStage, commit, and push code changes with conventional commit messages.
dtbuchholzStage Git changes, create conventional commits, push branches, and open pull requests via GitHub CLI.
Lev-itConfigure Husky and lint-staged pre-commit hooks for linting, type checking, and tests.
dennisonbertramGenerate release notes from Git history using Conventional Commits and git-cliff.
