skills.rest
google
googleOFFICIAL
Explore all skills by this author →
Website𝕏@GoogleOSSGitHub

adk-git

Generate Conventional Commit messages with type/scope formatting for adk-python git operations.

21.1k|3.8k|Updated Apr 1, 2025
Search Tags:#git#code review#conventional commits#commit messages#branching#release notes#pull requests
One-click install
npx skills add https://github.com/google/adk-python --skill adk-git
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adk-git
Source: https://github.com/google/adk-python/tree/main/.agents/skills/adk-git
Command: npx skills add https://github.com/google/adk-python --skill adk-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you produce consistent, review-friendly Git commits for adk-python so changes are easier to understand, track, and merge.

Core Features & Use Cases

  • Conventional Commits enforcement: Use a structured commit format with clear types and scopes to keep history readable.
  • Why-first subject line guidance: Write subjects that explain motivation and outcome, not just the mechanical change.
  • Clear body conventions: Add context that explains the reason and, when relevant, references GitHub issues to improve traceability.
  • Operation coverage: Supports the full range of git operations (commit, push, pull, rebase, branching, PRs, cherry-picks) using the same commit message conventions.

Quick Start

Use the adk-git skill to write a conventional commit message like feat(workflow): Support JSON string parsing in schema validation, then include a short body explaining why the change was needed.

Frequently Asked Questions about adk-git

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write conventional commit messages for git operations?▼

Conventional commit messages require a structured type and scope, a why-first subject line of 50 characters or less, an optional explanatory body, and issue references when applicable. This format keeps feature development, bug fixing, and refactoring changes review-friendly and trackable.

What is the best way to format git commit subjects for code review?▼

The best way to format git commit subjects is using a why-first approach that explains motivation and outcome rather than the mechanical change. Keep the subject line to 50 characters or less, preceded by a clear type and scope, to make changes easier to understand and merge.

When do I need to include issue references in a commit message body?▼

Issue references should be included in a commit message body when applicable to improve traceability. The body provides context explaining the reason for the change, connecting your documentation, CI, or feature updates to their relevant tracking issues.

Can I use conventional commits for branching and pull requests?▼

Yes, conventional commits apply to the full range of git operations including branching, pull requests, cherry-picks, and rebasing. Using the same commit message conventions across all operations ensures consistent history tracking for code reviews.

Does this commit format support refactoring and CI chore changes?▼

Yes, this commit format supports refactoring, documentation, and CI or chore changes that must be reviewed and tracked over time. You must apply the type and scope formatting to these operations just as you would for feature development or bug fixing.

Related Skills

Explore More Software Engineering Skills→
d0whc3rd0whc3r
2

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
Fandry96Fandry96
27

git-pushing

Stage changes, generate conventional commits, and push to a remote Git repository.

Community
Intermediate
Tonybleything76Tonybleything76

Changelog Generator

Generate changelog entries from Git commit history using Conventional Commits.

Community
Advanced
lexicalninjalexicalninja
2

git-commit-helper

Analyze staged changes to generate conventional commit messages.

Community
Intermediate