ワンクリックで
explain-flow
Analyze and explain code flow in openstack-k8s-operators operators with automated parsing and visual diagrams
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Analyze and explain code flow in openstack-k8s-operators operators with automated parsing and visual diagrams
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | explain-flow |
| description | Analyze and explain code flow in openstack-k8s-operators operators with automated parsing and visual diagrams |
| argument-hint | [directory] |
| user-invocable | true |
| allowed-tools | ["Read","Grep","Glob","Bash"] |
| context | fork |
This skill provides comprehensive code flow analysis for openstack-k8s-operators operators using automated parsing and visual representation.
When explaining code flow, I will:
The skill analyzes:
# Focus on reconcile functions
grep -r "func.*Reconcile" --include="*.go" .
I will generate:
func (r *Reconciler) Reconcile(ctx context.Context, req ctrl.Request)client.Get(), client.Create(), client.Update(), client.Delete()ctrl.Result{RequeueAfter: time.Duration}if err != nil blocksreturn ctrl.Result{}, errInvoke /explain-flow with:
The skill will automatically parse the code, extract flow patterns, and provide visual representations with actionable insights.
Scaffold RHOSO Deployment Topologies/Validated Architectures for the architecture repo with existing DT/VA analysis, kustomize generation, and staged automation
Interactive onboarding for openstack-k8s-operators — teaches Kubernetes operator fundamentals from scratch and tours the current operator repo at the learner's pace
Produce an analysis of observed problems in a must-gather report from OpenStack Services on OpenShift
Produce an analysis of observed problems in downloaded Zuul CI logs
Code review agent for openstack-k8s-operators following dev-docs conventions, lib-common patterns, and openstack-k8s-operators best practices
Validate CVE Jira tickets against the current codebase — assess reachability, exploitability, and recommend action (Go bump vs dependency bump vs code fix)