Inspect git status, diffs, and logs to write repository-compliant commit messages.
npx skills add https://github.com/agentty-xyz/agentty --skill git-commit-agentty-xyz
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/agentty-xyz/agentty/tree/main/skills/git-commit Command: npx skills add https://github.com/agentty-xyz/agentty --skill git-commit-agentty-xyz
Many commits lack necessary context, clear titles, or adherence to repository-specific conventions which makes review, history tracing, and collaboration harder; this skill helps gather context and craft commit messages that follow the project's rules.
Run git status, git diff, and git log -n 3 to collect context, then write a concise present-tense title and an optional body that explains why and how the change was made while following repository rules.
High-intent search queries and answers about installing and using this skill.
A repository-compliant commit message requires a concise present-tense title and an optional body explaining why and how changes were made, formatted by inspecting git status, diffs, and recent logs to adhere to project rules.
Gather commit context by running git status, git diff, and git log -n 3 to collect working tree changes and recent repository history, ensuring the commit message accurately reflects the current modifications.
You should avoid Conventional Commit prefixes when repository conventions require omitting them, instead writing a concise present-tense title and optional body without specific prefix formatting to maintain compliance.
Bypassing pre-commit hooks with --no-verify is prohibited by repository rules enforcement, which requires all tooling and validation checks to pass naturally before changes are committed to the repository.
You must omit Co-Authored-By trailers and AI attribution in commit messages, as repository conventions require excluding both to maintain a clean and standardized version control history.
Git commit history lacks clear context when messages are created without inspecting git diffs and recent logs, resulting in titles and bodies that fail to explain why and how changes were made according to repository conventions.
borkwebGenerate conventional git commit messages from staged diffs and repository history.
latestaiagentsSynchronize documentation with code changes across inline comments, API references, and README files.
leafcoderStandardize Git practices and collaboration workflows across GitHub and Gitee.
handsomelong922Enforce development conventions and conventional commit patterns for everything-claude-code.
