What problem does it solve?
BK-CI pipeline and authoring-flow configurations are stored as deeply nested Model JSON (Model -> Stage -> Container -> Element), which is hard to read directly. This Skill helps an AI explain what a pasted pipeline JSON actually defines: startup parameters, job types, plugin behavior, matrix expansion, Finally stages, and review gates.
Core Features & Use Cases
- Model Structure Decoding: Restores raw JSON into the four-layer Model -> Stage -> Container -> Element hierarchy and explains each layer's role.
- Plugin Semantics: Interprets built-in elements (linuxScript, windowsScript, CODE_GIT, manualReviewUserTask, subPipelineCall) and store plugins (marketBuild/marketBuildLess) via atomCode, data.input, and data.output, with conservative handling of unknown atomCodes.
- Control Flow Explanation: Clarifies runCondition enums at Stage/Job/Element levels, matrix expansion, mutex groups, checkIn/checkOut reviews, and disabled nodes.
- Use Case: A user pastes a pipeline JSON and asks "what does this pipeline do?" The Skill explains the startup parameters from TriggerContainer.params, walks through each Stage and Job, and summarizes the overall flow and likely outputs.
Quick Start
Paste your BK-CI pipeline Model JSON and ask the AI to explain what this pipeline does, including its startup parameters, stages, jobs, and plugins.