What problem does it solve? Adding support for new log types in Kubernetes History Inspector (KHI) requires navigating a strict DAG task architecture with contract/implementation package separation, and mistakes cause circular imports or broken task registration. This Skill provides the exact package patterns, code templates, and testing strategies to implement log parsers correctly. ## Core Features & Use Cases - Package Structure Enforcement: Defines the contract package (taskid.go, extractor.go, timeline_type.go) versus implementation package (impl/ with form.go, query.go, ingester.go, mapper.go, registration.go) boundaries to prevent circular imports. - Complete Pipeline Templates: Provides working Go code for all four DAG steps: form tasks, Cloud Logging query tasks, log ingesters, and timeline mappers, including the advanced ManifestLogToTimelineMapper for multi-resource state tracking. - Testing Strategies: Includes table-driven test patterns for ingesters, mappers, and chronological multi-group merge validation using mock logs and fluent ChangeSet assertions. - Use Case: When you need to add support for a new log source (e.g., a custom application writing to Cloud Logging), follow the step-by-step samples to create the contract package, implement the four pipeline tasks, register them, and write unit tests. ## Quick Start Use the khi-parser skill to add a new log parser for my custom application logs under pkg/task/inspection/googlecloud/customapp.
