// Use for any git operation (commit, push, pull, rebase, branch, PR, cherry-pick, etc.). Provides commit message format and conventions.
Central hub for building, testing, and iterating on ADK agents. Trigger this skill when the user wants to create a new agent, configure modes (task, single-turn), or build graph-based workflows.
ADK architectural knowledge — graph orchestration, resumption, execution flow, node contracts, observability, and LLM context orchestration. Use this skill whenever you need to understand the architecture, event flow, or state management of the ADK system, or when designing or modifying core components. Triggers on "how does X work", "design of", "architecture of", "event flow", "resumption state", "checkpoint", "BaseNode", "NodeRunner".
Use when debugging ADK agents, inspecting sessions, testing agent behavior, troubleshooting tool calls, event flow issues, or diagnosing LLM/model problems.
Author new samples for the ADK Python repository. Use this skill when the user wants to create a new sample demonstrating a feature or agent pattern (e.g., dynamic nodes, standalone agents, fan-out/fan-in) or when adding examples to subdirectories under `contributing/`.
Set up a local development environment for the ADK Python project. Use when the user wants to get started developing, set up their environment, install dependencies, or prepare for contributing.
ADK development style guide for routine nits — Python idioms, codebase conventions, imports, typing, Pydantic patterns, formatting, logging, and file organization. Use this skill whenever writing code, tests, or reviewing PRs for the ADK project to ensure compliance with styling and coding conventions. Triggers on "code style", "how should I format", "naming convention", "lint", "nit", "imports", "typing", "Pydantic patterns", "testing rules".
| name | adk-git |
| description | Use for any git operation (commit, push, pull, rebase, branch, PR, cherry-pick, etc.). Provides commit message format and conventions. |
Use Conventional Commits:
<type>(<scope>): <description>
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Formatting, no code changerefactor: Code restructure without behavior changeperf: Performance improvementtest: Adding/updating testschore: Build, config, dependenciesci: CI/CD changesCRITICAL: The subject line must answer why, not just what. A reviewer reading only the subject should understand the motivation.
Fix race condition when two agents write to same sessionUpdate session.py to add lockSupport parallel tool execution in workflowsAdd asyncio.gather call in execute_tools_nodeMake graph public for dev UI serializationMake graph a public field on new WorkflowPrevent duplicate events when resuming HITLCheck interrupt_id before appendingPromote detailed commit messages by including a short, concrete explanation in the body:
Example (Feature):
feat(workflow): Support JSON string parsing in schema validation
Automatically parse JSON strings into dicts or Pydantic models when input_schema or output_schema is defined on a node.
Example (Fix):
fix(sessions): Prevent duplicate events when resuming HITL
The interrupt_id was not checked before appending, causing duplicates if the user resumed multiple times. Added a check to ignore already processed interrupts.
Self-check before committing: read your subject line and ask "does this tell me why someone made this change?" If it only describes what changed, rewrite it.
feat(agents): Support App pattern with lifecycle plugins
fix(sessions): Prevent memory leak on concurrent session cleanup
refactor(tools): Unify env var checks across tool implementations
docs: Add contributing guide for first-time contributors
[!IMPORTANT] Before performing any commit, check if
pre-commitis installed and configured with the expected hooks (isort,pyink,addlicense,mdformat). If not, remind the user to set up pre-commit hooks using theadk-setupskill.