Standardize Git commit messages and PR descriptions with Conventional Commits format.
npx skills add https://github.com/zoonk/zoonk --skill zoonk-commit
Please help me install this Agent Skill. Skill: zoonk-commit Source: https://github.com/zoonk/zoonk/tree/main/.agents/skills/zoonk-commit Command: npx skills add https://github.com/zoonk/zoonk --skill zoonk-commit
Guidelines to standardize how developers describe changes via commits and PR descriptions, reducing ambiguity and improving code reviews.
Compose a concise, properly formatted commit message for the latest change.
High-intent search queries and answers about installing and using this skill.
Consistent git commit messages use a structured format like type(scope): short message to categorize changes. This reduces ambiguity during code reviews by conveying the exact nature of software development updates clearly.
A conventional pull request description categorizes changes using defined types and scopes. This structured messaging approach ensures reviewers understand the context and purpose of the software development modifications quickly.
Standardizing commit messages and PR summaries reduces ambiguity and improves code reviews. It conveys changes with a conventional, consistent format, ensuring all developers understand the modifications across the codebase.
Git commit message types and scopes categorize the specific changes made to the codebase. The guidelines define these categories to provide structured message formatting and best practices for software development.
chaimtInitialize a Git repository with an initial commit in the current directory.
koumatsumotoAutomate GitHub branch creation, review, commit, push, and pull request workflows.
vulikjulikGenerate conventional commit messages from staged git changes.
julianromliAnalyze git commit history to generate structured customer-facing release notes.
