repo-development
Maintain, test, regenerate, and troubleshoot a Kubeflow Pipelines source checkout without confusing checkout work with public KFP package usage.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-08
- Stars
- ★ 11
- Forks
- 3
01 前言 Front Matter
- name
- repo-development
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Maintain, test, regenerate, and troubleshoot a Kubeflow Pipelines source checkout without confusing checkout work with public KFP package usage.
- disable-model-invocation
- true
02 资源文件 4
- 参考文档references/architecture-and-layout.md8.9 KB
- 参考文档references/development-testing.md11.0 KB
- 参考文档references/generated-code.md8.5 KB
- 参考文档references/troubleshooting.md12.8 KB
03 SKILL.md 正文
Kubeflow Pipelines Repo Development
Use this sub-skill only when the user is working on the Kubeflow Pipelines source repository: editing code, tests, generated files, CI, manifests, frontend assets, backend services, or checkout-local developer setup.
For public package use, route away instead of answering here:
- Writing KFP components, pipelines, artifacts, control flow, local execution, task modifiers ->
pipeline-authoring. - Compiling pipeline files,
Compiler().compile,kfp dsl compile,dsl-compile, PipelineSpec output ->compiler-and-cli. kfp.Client, uploads, runs, recurring runs, experiments, registry, service auth ->client-and-registry.from kfp import kubernetes, secrets, PVCs, tolerations, node selectors, pod labels, Kubernetes task configuration ->kubernetes-platform.- Other AI workflow libraries or different repositories -> use that repository's skill or ordinary repo inspection.
Operating Rules
- Confirm the task is checkout maintenance. If the user is trying to use an installed
kfppackage, route to the public-use sub-skill above. - Treat the bundled references as the operating baseline, then verify against the current checkout before running commands because Make targets, workflow matrices, and package versions may have changed.
- Obey any current checkout agent instructions and keep changes minimal. Preserve DCO/PR conventions and project style.
- Never hand-edit generated outputs. Change the source artifact and run the documented regeneration command from references/generated-code.md.
- Choose the narrowest safe command family from references/development-testing.md. Do not run cluster, Docker, GCP, release, cleanup, or credential-bound commands unless the user explicitly asked for that scope and prerequisites are available.
- When a repo edit changes public SDK behavior, update or test the corresponding public-use path too: authoring examples, compile behavior, client flows, or
kfp-kubernetestask config. - Record skipped checks honestly. Go, Node, Docker, Kind, kubectl, Ginkgo, and GPU/Kubernetes lanes are prerequisite-bound; a CPU import or compile check does not verify those lanes.
Reference Map
- references/architecture-and-layout.md: monorepo areas, package/version relationships, backend/frontend/runtime roles, and contribution conventions.
- references/development-testing.md: local setup, tool prerequisites, targeted test/format/build command families, frontend smoke testing, and dependency updates.
- references/generated-code.md: generated-file ownership, regeneration commands, CI drift checks, and frontend/backend API-client drift handling.
- references/troubleshooting.md: symptom-oriented fixes for generated drift, missing tools, cluster/e2e failures, frontend lockfile/API drift, GPU labels,
_KFP_RUNTIME=true, dependency locks, and formatting failures.
Safe Handoff Pattern
When answering a repo-maintenance task, include:
- changed area and owning paths;
- commands run and commands intentionally skipped with prerequisites;
- generated-code commands needed or not needed;
- public-package routes that may need examples/tests updated;
- CI lanes most likely to cover the change;
- any maintainer-only, credential-bound, destructive, or cluster/GPU-dependent gaps.
This sub-skill is self-contained. It names relative paths that should exist in a Kubeflow Pipelines checkout, but it does not require the original construction checkout or any absolute source path.
04 同仓库更多 Skills
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
python-api
Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP/mAP semantics, and source-style import diagnostics.
file-evaluation
Folder-based PASCAL VOC AP/mAP evaluation from ground-truth and detection text files.
object-detection-metrics
Guides legacy Object-Detection-Metrics PASCAL VOC AP/mAP evaluation from detection text folders and direct Python API classes.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.