// Provides a structured logic for capturing and routing agentic learnings to prevent knowledge pollution.
Moves a mockgcp service from using locally generated grpc-gateway proto bindings to using reflection with the official Google Cloud Go client library (httptogrpc). Use this when tasked with stopping grpc-gateway generation for a GCP service in mockgcp.
Creates or updates the _identity.go and _reference.go files for a Config Connector resource, ensuring they follow the canonical gcpurls.Template pattern. Use this when you need to make sure the identity and reference is up to date for a KCC resource or when implementing IdentityV2 and refs.Ref for a resource.
Implement the controller, mappers, and fuzzer for a direct KCC resource, ensuring package isolation and CI compliance. Use this when implementing the main reconciliation logic for a "direct" resource.
Guides the implementation of KRM types and CRD scaffolding for new "direct" resources.
Provides instructions and a tool for analyzing Custom Resource Definition (CRD) changes, including checking for KRM API structural equivalence and backward compatibility.
Checks apis/ subdirectories for missing generate.sh and helps create PRs to add them, following the pattern in
| name | kcc-agentic-journaler |
| description | Provides a structured logic for capturing and routing agentic learnings to prevent knowledge pollution. |
As an agent, you must record "tribal knowledge" and technical breakthroughs. This skill ensures that your learnings are stored in the most contextually relevant location.
When you have a new learning, follow this hierarchy to choose the destination:
Scenario: You found a better way to do something that applies to all KCC resources (e.g., "A more efficient way to resolve Project IDs").
Destination: Update the relevant Skill's SKILL.md file directly.
Scenario: You found a trick for a specific implementation area, or a quirk unique to a specific GCP service.
Destination: ALWAYS create or append to .gemini/journals/<service_name>.md.
CRITICAL: Do NOT append to any journal.md inside a .gemini/skills/ directory. Multiple agents working in parallel on different services will cause merge conflicts if they all write to a centralized skill journal. By keeping journals scoped to the <service_name>, we eliminate cross-service merge conflicts.
Use this format for your entries in .gemini/journals/<service_name>.md:
### [YYYY-MM-DD] <Brief Title>
- **Context**: <What were you implementing? Link to Kind/PR>
- **Problem**: <What was the unexpected behavior or hurdle?>
- **Solution**: <How did you solve it? Provide code snippets if relevant.>
- **Impact**: <Why should the next agent care about this?>
In your final turn of the task, you MUST state which knowledge was captured and provide the file path.