Create atomic git commits following the conventional format.
npx skills add https://github.com/alxxpersonal/forge --skill commit-forge
Please help me install this Agent Skill. Skill: commit-forge Source: https://github.com/alxxpersonal/forge/tree/main/skills/commit-forge Command: npx skills add https://github.com/alxxpersonal/forge --skill commit-forge
Ensures that git history remains clean and understandable by enforcing atomic, descriptive commits that reflect a single logical change, reducing review time and confusion.
Create a single, atomic commit describing the latest change in the repository.
High-intent search queries and answers about installing and using this skill.
To automate atomic git commits, this tool enforces a one-change-per-commit rule and standardizes the subject, body, and footer structure using conventional types like feat, fix, and docs to maintain a clean version-control history.
An atomic commit represents a single logical change in your version-control history. You need it to keep git history understandable, which reduces review time and prevents confusion when tracking specific features or fixes.
Formatting conventional commit messages requires a type(scope): description structure. This tool supports common types like feat, fix, refactor, and chore, while applying guardrails to block risky flags and ensure a standardized subject, body, and footer.
No, you cannot use co-author tags or skip git hooks. This enforces guardrails that block co-author tagging and risky flags to promote deliberate, reviewed commits and maintain strict version-control best practices.
The best way to enforce a one-change-per-commit rule is to automate the staging and commit process with strict guardrails. This tool prevents risky actions and requires a conventional commit format, ensuring each commit reflects a single logical change.
Yes, you need to stage changes first. This applies to developers who stage changes or complete tasks, taking those staged changes and formatting them into a clean, atomic conventional commit with a standardized structure.
GLaDO8Generates concise Git commit messages and commits staged or unstaged changes.
vineet-codes256Organize staged and unstaged changes into atomic git commits and push them.
nathanperkinsGuide code review, run formatting and linting checks, and suggest conventional commit messages.
sprabyGenerate git commit messages from staged changes with automatic detection of commit type and a concise, human-readable summary of the intended semantic changes.
