Generate conventional git commits from uncommitted changes with why-context.
npx skills add https://github.com/addisonbeck/nix --skill write-git-commit
Please help me install this Agent Skill. Skill: write-git-commit Source: https://github.com/addisonbeck/nix/tree/main/bobert/skills/write-git-commit Command: npx skills add https://github.com/addisonbeck/nix --skill write-git-commit
Creates high-quality git commits from uncommitted changes following conventional commit standards. Analyzes diffs, requires user-provided "why" context, matches local repository style, detects splitting opportunities, and executes pre-commit verification. Use when committing changes during development or reflect phases.
Generate a conventional git commit for my current uncommitted changes, including the motivation why, optional scope, and a concise, well-formed subject with a detailed body.
High-intent search queries and answers about installing and using this skill.
You can generate a conventional git commit by applying this Skill to your uncommitted changes. It analyzes your diffs, requires you to provide motivational why-context, matches local repository style, and runs pre-commit verification before assembling the final message.
The best way to automate conventional commit formatting is using a Skill that orchestrates the full commit lifecycle. It interprets diffs, enforces type and scope rules, and provides explicit staging guidance to ensure compliance with repository conventions.
To split large diffs into cohesive commits, the Skill detects splitting opportunities during diff analysis and advises a split workflow. This ensures large changes are broken into logical, convention-compliant commits.
Yes, you need to provide motivational why-context for automated git commit generation. The Skill enforces input validation and requires user-provided context to craft a high-quality commit message that explains the reasoning behind the changes.
Yes, you can run pre-commit checks automatically when generating a git commit. The Skill executes pre-commit verification as part of its lifecycle orchestration, ensuring your changes pass checks before final staging and execution.
Yes, this conventional commit tool works with existing repository styles. During context gathering, it matches local repository conventions and enforces compliance to ensure generated messages align with your project's formatting standards.
xjiang77Generate conventional Git commit messages with Chinese descriptions from staged changes.
Room-CStage, format, and push git changes with conventional commits.
Fandhe-AIAutomate code review via git diff analysis for quality and security.
rseGenerate a concise commit message from `git diff --cached` output.
