AutoGineer
Generated banner for Open Knowledge Format for Crossplane v2
Generated logo for Open Knowledge Format for Crossplane v2

Open Knowledge Format for Crossplane v2

LLM wiki kit

First committed by jkroepke

Published in jkroepke/okf-crossplane-v2. Publisher page

37 GitHub stars

What it is

LLM-wiki in OKF (Open Knowledge Format) for Crossplane v2
— the description by jkroepke

AutoGineer overview, from the brain’s own files

The okf-crossplane-v2 repository provides a versioned, source-backed knowledge catalog designed to help AI agents and developers navigate the Crossplane v2 ecosystem. It aggregates information from Go API types, CRDs, package metadata, and documentation into a structured format. By utilizing the Open Knowledge Format (OKF), it enables agents to perform precise lookups on providers, composition functions, and API definitions. The project includes a dedicated MCP server that allows agents to query live repository data, such as CRD definitions, versioning, and examples, ensuring that the information retrieved is grounded in specific, versioned source code.

How it works

Memory model: LLM wiki

AutoGineer overview, from the brain’s own files

The system organizes technical knowledge into a catalog of Markdown files stored in the catalog folder. These files contain OKF metadata and provenance links. An MCP server, which can be self-hosted or used via a public endpoint, ingests this catalog into a DuckDB instance. Agents interact with this data through specific tools that resolve provider versions, search CRDs, and retrieve documentation or examples. The system relies on specialized researcher agents defined in the .agents folder to maintain and validate the knowledge base, ensuring that facts are linked to stable source code and documentation.

Folders
FolderRoleFiles
.codexagent-config25
.githubagent-config2
skillsagent-instructions1
.agentsfolder37
.codex-pluginfolder1
.okffolder2
.pifolder27
.pluginfolder1
catalogfolder120
mcpfolder12

Requirements

Apps: Docker

API keys (by name): GITHUB_TOKEN

Works with: Claude Code, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Amp, Cline, JetBrains Junie, Devin (ex-Windsurf)

Set it up

  1. Download the brain as a ZIP and unzip it where you keep your notes or project: https://mp-staging.autogineer.com/agent-brains/jkroepke/okf-crossplane-v2/download

  2. Point Claude Code at .codex-plugin/plugin.json: it does not read that file on its own.

  3. cd okf-crossplane-v2 && claude

  4. AutoGineer scanned these files at commit df24ac2.

  5. Add crossplane-v2-okf to .mcp.json:

    {
  "mcpServers": {
    "crossplane-v2-okf": {
      "type": "http",
      "url": "https://crossplane.mcp.jkroepke.de/mcp"
    }
  }
}

  6. Or add it with the Claude Code CLI:

    claude mcp add --transport http crossplane-v2-okf https://crossplane.mcp.jkroepke.de/mcp

  7. Your data is sent to crossplane.mcp.jkroepke.de.

  8. First committed by jkroepke. Published in jkroepke/okf-crossplane-v2. Licence: Apache License 2.0.

Usage

AutoGineer overview, from the brain’s own files

  • Querying CRD definitions for specific Crossplane providers
  • Retrieving versioned examples for composition functions
  • Resolving stable provider versions and their associated documentation
  • Integrating Crossplane knowledge into AI agent workflows via MCP
“Find the latest version of the AWS provider and list its CRDs.”
The agent uses the get_versions and provider_crd_search tools to return the canonical repository name and a list of available CRDs for the specified provider.
“Show me the definition for the S3Bucket CRD in the latest AWS provider.”
The agent retrieves the YAML definition of the requested CRD using the provider_crd_get_definition tool, ensuring the output is token-efficient.

Documentation by jkroepke

Image: CI Image: GitHub license Image: GitHub Repo stars Image: BundleDex

Open Knowledge Format for Crossplane v2

This repository provides a structured knowledge catalog for the Crossplane v2 ecosystem using Open Knowledge Format v0.2.

The goal is to make Crossplane concepts, APIs, providers, composition functions, documentation, and practical examples easier to discover and understand. The catalog is designed for both humans and knowledge-aware tools.

Installation

WARNING
The public MCP server is a temporary early-access service for early adopters. Its availability is not guaranteed, and it may change or be removed without notice. It is intended to bridge the current tooling gap until the OKF ecosystem provides practical, end-user-friendly solutions that run locally. For reliable or production use, self-host the included container.

Install the companion skill and hosted OKF-aware MCP server together as a plugin for every detected supported agent:

npx plugins add jkroepke/okf-crossplane-v2

Pass --target codex to install only in Codex. Restart the selected agents after installation.

Alternatively, install the hosted OKF-aware MCP server globally:

npx add-mcp \
  https://crossplane.mcp.jkroepke.de/mcp \
  --name crossplane-v2-okf \
  --global

Then install the companion skill so the agent prefers this bundle over generic documentation providers for Crossplane v2 questions:

npx skills add jkroepke/okf-crossplane-v2 \
  --skill crossplane-v2-okf \
  --global

Both standalone installers detect supported agents and ask where the integration should be installed. Restart the selected agent after installation.

The public MCP health endpoint is available at https://crossplane.mcp.jkroepke.de/healthz.

Self-hosting the MCP server

The included container fetches this repository, ingests catalog/ into a DuckDB catalog, and serves the okf-mcp tools over Streamable HTTP.

docker compose up --build --detach

To authenticate the server's GitHub requests, export GITHUB_TOKEN before starting the container. The token is optional.

The local MCP endpoint is http://127.0.0.1:8000/mcp. Put it behind a TLS reverse proxy for crossplane.mcp.jkroepke.de.

The catalog is refreshed at container startup. If fetching or ingestion fails and a previous catalog exists in the volume, the server continues with that last successful catalog.

The MCP tools are read-only, but the public endpoint has no application-level authentication. Apply request limits and access controls at the reverse proxy when required.

Crossplane package tools

The server adds these tools backed by OSS GitHub repositories:

  • get_versions(name) resolves an OSS provider or function repository and returns its canonical repository name, versions.latest, a compact list of recent stable versions, and tag counts. Pass the returned provider name to the CRD tools.

  • provider_crd_search(provider_name, provider_version, crd_search_term) searches CRDs in one explicit provider package version. The search term supports case-insensitive shell-style wildcards.

  • provider_crd_get_definition(provider_name, provider_version, crd_name, path?) returns the complete CRD definition as token-efficient YAML. Use a dotted path such as .spec or .spec.versions[0] to return only a subtree.

  • provider_crd_get_examples(provider_name, provider_version, crd_name) returns GitHub repository paths for generated and handwritten examples. Without an API version, it selects the latest served CRD API version, for example examples-generated/namespaced/ec2/v1beta2/route.yaml.

  • provider_crd_get_terraform_docs(provider_name, provider_version, crd_name) returns the Terraform provider repository, version, and documentation path. It reads the Crossplane provider Makefile and the generated controller mapping instead of inferring the Terraform resource name.

crd_name accepts a Kind, group/Kind, group/version/Kind, or a YAML fragment containing apiVersion and kind.

Use an OSS GitHub repository name such as crossplane-contrib/provider-upjet-aws or crossplane-contrib/function-go-templating. A small set of historical package aliases is mapped to their known OSS source repositories; unmapped upbound/... names are rejected rather than guessed.

The CRD tools require an explicit provider version. The value latest is also supported and selects the highest stable semantic-version Git tag. Self-hosted deployments need outbound HTTPS access to GITHUB_API_URL and GITHUB_RAW_URL.

Successful remote fetches are cached in memory. Git tag listings use the configurable short FETCH_CACHE_TTL_SECONDS (default: 300 seconds); CRDs, definitions, examples, and Terraform metadata resolved at immutable Git tags are cached for 30 days. FETCH_CACHE_MAX_ENTRIES (default: 512) bounds memory use.

Why this repository exists

Crossplane knowledge is distributed across many repositories and kinds of sources:

  • Go API types and runtime implementations

  • CustomResourceDefinitions and OpenAPI schemas

  • package metadata

  • tests and executable examples

  • official Crossplane documentation

  • community implementations and real-world composition examples

Upjet-based providers add another layer. Their Crossplane managed resources are generated from Terraform provider resources, while the Terraform documentation often contains more details about the underlying cloud APIs and configuration fields.

This repository connects these sources in one versioned catalog without replacing the original documentation.

Knowledge structure

Knowledge is stored as small Markdown documents under catalog/. Each document represents an independently useful concept and includes OKF metadata, provenance in sources, keyed claim footnotes, and relationships to related concepts.

Repository validation pins okf-ingest 0.11.0, which adds OKF v0.2 core support, including generated.at freshness fallback and preservation of the new frontmatter families (upstream support commit).

If the task is to build a Crossplane v2 Composition, start with the Composition developer route. It routes agents through separate API/provider, pipeline/security, and testing/packaging concepts without pretending that provider-specific schemas or credentials are universal.

The catalog is intended to be:

  • Source-backed: important statements link to source code, schemas, tests, examples, or official documentation.

  • Version-aware: sources are tied to specific repository revisions.

  • Navigable: overview documents connect related concepts without requiring readers to know the source repository layout.

  • Incremental: providers, functions, services, documentation areas, and example repositories can be added in focused batches.

License

This project is licensed under the Apache License 2.0.

catalog/log.md

Catalog Update Log

2026-10-16

  • Creation: Added xprin v0.5.0 function container reuse, on by default with --no-container-reuse to opt out.

  • Creation: Added xprin --crossplane-version pinning, available since xprin v0.3.0, for render and validation image tags.

  • Creation: Added xprin Crossplane CLI tier detection, available since xprin v0.3.0, which chooses the validate subcommand and render flags.

  • Creation: Added the xprin test --artifacts-dir export, available since xprin v0.3.0, and distinguished it from id-based test chaining.

  • Creation: Added the xprin update-goldens command, available since xprin v0.3.0, for regenerating diff and dyff golden files.

  • Update: Recorded that CLI v2.5.0 crossplane resource validate strictly decodes Kubernetes built-in resources without supplied definitions, and scoped the earlier missing-definition guidance to v2.4.0.

  • Creation: Added the CLI v2.5.0 features.generateGoRuntimeObjects setting that makes control plane project Go models implement runtime.Object with per-package AddToScheme helpers.

  • Creation: Added the CLI v2.5.0 features.generateGoModelAccessors setting that generates GetX and SetX accessors on control plane project Go models.

  • Update: Documented the CLI v2.5.0 crossplane xrd generate --replace flag for regenerating an XRD in a control plane project.

  • Update: Documented CLI v2.5.0 SimpleSchema customTypes for crossplane xrd generate and the naming difference from kro types.

  • Creation: Added the Beta crossplane xrd convert command with its CLI v2.5.0 --format=jsonschema output for YAML language server validation.

  • Creation: Added function-go-templating v0.13.0 function-wide default template options and the MAX_RECV_MESSAGE_SIZE setting, and recorded that PR #593 is now contained in v0.13.0.

  • Creation: Added the function-go-templating v0.13.0 response TTL concept covering the --ttl flag, the Beta ttl input field, and the XR TTL annotation.

  • Update: Recorded that function-go-templating v0.13.0 accepts Unknown as an alias for Unspecified in the ready annotation.

  • Update: Documented the function-go-templating v0.13.0 getComposedConnectionDetails helper and linked it from the composed connection-details Secret pattern.

2026-09-05

  • Correction: Distinguished the Beta crossplane project command workflow from the Alpha dev.crossplane.io/v1alpha1 Project metadata API, and made the project-versus-standalone question explicit in the agent-facing Crossplane skill.

2026-08-21

  • Creation: Added an explicit opt-in decision for wrapping new Compositions as Beta Crossplane control plane projects, while preserving and clarifying the standalone manifest route.

  • Creation: Added a provider-development SDK route from an immutable provider-template snapshot through modern managed-resource APIs, ProviderConfig and credentials, typed reconciliation, generation, testing, and xpkg packaging.

  • Creation: Added a user-selected function-kro v0.3.0 preview reference for the package, Alpha ResourceGraph input, and graph evaluation behavior, backed by the exact KRO v0.9.2 documentation selected in go.mod.

2026-08-20

  • Migration: Migrated the catalog to OKF v0.2 by replacing legacy timestamps with generation metadata and moving numbered citation lists into frontmatter provenance with keyed claim footnotes.

2026-08-19

  • Creation: Added release-pinned SDK guidance for crossplane-runtime's opt-in custom-resource gate CRD cache transform and its shared-cache data boundary.

2026-07-19

  • Removal: Removed the reusable readiness-gated desired-resource-introduction pattern and its template-latch, Bucket-stage, and authoring-choice guidance. The function-sequencer reference now documents behavior without recommending creation gating.

2026-07-18

  • Update: Added a Composition-authoring default that prefers the Upjet AWS, Azure, and GCP providers for new work while retaining already-used non-Upjet providers unless a tested, resource-by-resource migration is explicitly planned.

  • Creation: Documented how to retrieve Crossplane provider-published connection Secret keys from release-pinned implementation sources, distinguishing destination-only CRD fields from AdditionalConnectionDetailsFn behavior and preserving conditional-key boundaries.

  • Update: Extended provider connection-detail retrieval with the typed managed.ConnectionDetails and runtime-publisher path used by provider-sql, separating it from Upjet-based Crossplane provider configuration.

2026-07-16

  • Reorganization: Kept readiness concepts atomic while expanding the Composition developer route by outcome, grouping function-go-templating patterns by the state they change, and renaming the Sveltos specialization so it cannot be mistaken for the generic non-composed-resource pattern.

  • Update: Taught the Crossplane v2 OKF skill to retrieve the Composition developer starter as the primary routing concept for Composition authoring and substantial review tasks.

  • Review: Added an evidence-bounded Composition developer starter route and cross-concept links across API design, provider schema selection, functions, security, readiness, identity, testing, and packaging.

  • Correction: Replaced the incorrect XRD v2 storage authoring field with referenceable and corrected the Composition compositeTypeRef formula.

  • Correction: Assigned ExtraResources read RBAC to the Crossplane Core service account and separated required-resource reads from composed-resource writes and Function runtime identity.

  • Consistency: Scoped feature-state defaults to their owning API or capability; unlabelled non-API packages, helpers, and implementation behavior now remain Not stated.

  • Cross-concept review: Distinguished readiness, desired-resource introduction, and deletion protection; documented Secret existence versus key completeness and shared environment-context ownership.

  • Validation: Replaced directory links with explicit indexes and pinned remaining released-source citations to immutable commits.

  • Creation: Proved composed-resource name preservation under a stable logical key, bounded immutable-field recreation claims, and added staged create-before-delete replacement guidance.

  • Creation: Added complete function-sequencer v0.6.0 Input property coverage, explicit UsageVersion mixed-scope safety, and post-release createOnly boundaries.

  • Update: Cross-linked Core Usage/ClusterUsage scope guidance with function-sequencer issue #114 and generated-reference limitations.

  • Update: Added local validation schema-coverage triage for built-in Kubernetes resources, non-Crossplane custom resources, and community CRD catalog discovery boundaries.

  • Creation: Added release-pinned function-sequencer knowledge covering declared desired-resource sequencing, observed-successor retention, Input controls, and XR Events; clarified that manual template readiness does not sequence resource introduction.

  • Creation: Added Go-template whitespace-boundary guidance for multi-document function-go-templating output and YAML render verification.

  • Correction: Clarified that the XRD referenceable version, rather than an XRD storage field, determines the generated CRD storage version; confirmed a referenceable v1alpha1 renders as storage: true.

  • Update: Added release-contained PR #6588 source and test proof for the namespaced-XR cluster-scoped-resource rejection.

  • Creation: Added provider-kubernetes Object wrapper readiness and Secret-status boundaries, including Alpha API scope, derived-condition limits, and random-secret churn risk.

  • Update: Added dependency-gating, dynamic collection identity, and base64-safe connection-data guidance; excluded Claim-based workflows from this v2 pattern.

  • Creation: Added a strict function-go-templating pattern that gates database XR status and connection references on observed composed-resource readiness, distinguishes Kubernetes names from managed-resource external names, and excludes legacy v1 connection output.

  • Update: Added a template-side namespace-result filter for ExtraResources label lookups, including an early-stop Go-template variable pattern for use after the scan; it cannot scope the earlier cluster-wide list or reduce its RBAC requirement.

  • Creation: Added an Alpha External Secrets Operator PushSecret pattern for publishing selected platform-team Kubernetes Secret data to configured external secret stores, including Vault and AWS examples.

  • Update: Extended provider-family guidance with Upbound's pinned official-provider installation, monolith ownership, shared-family dependency, and offline-resolution boundaries.

  • Creation: Added provider CRD schema discovery guidance for version-addressed Upbound API routes, pinned source-tree fallbacks, and AWS package-identity boundaries.

  • Creation: Added Crossplane CLI local Composition rendering guidance, including Docker runtime requirements, Functions-only input handling, and observed-resource status fixtures.

  • Creation: Added an XR-focused xprin assertion-suite reference and a recommended empty-project manifest layout for Composition authoring.

2026-07-15

  • Creation: Added the accepted controlled-rollout design as historical context and separated its proposed Function-revision API from selected-release behavior proved by schemas and controller code.

  • Update: Clarified that generated managed-resource references are Provider- and field-specific, documented explicit observed-status composition fallbacks, and bounded server-side-apply ownership and re-resolution behavior.

  • Update: Added explicit ProviderConfig selection and central-account least-privilege guidance.

  • Creation: Added a release-pinned Upjet-to-Terraform provenance and example-adaptation evidence chain.

  • Update: Added MRAP default-activation, additive-overlap, one-way activation, and minimal-activation policy guidance.

  • Creation: Added evidence-backed AWS provider-family package identification and the v2.3 modern namespaced managed-resource group convention.

  • Creation: Established the provider catalog foundation: implementation families, AWS migration/selection boundaries, and Provider package revision activation scope.

  • Creation: Added tenant XR API-group and admission-security guidance, including organization-specific example conventions.

  • Creation: Added focused XRD-backed CRD authoring guidance for OpenAPI schemas, CEL validation, unknown data, version evolution, and scale/display subresources.

  • Update: Verified the XRD v2 Composition selection fields: documented default selection, automatic or manual revision policy, and immutable enforced Composition override behavior.

  • Reorganization: Separated namespaced Composition enforcement from cross-namespace synchronization patterns and moved real-time Composition and Management Policies project history into dedicated references.

  • Reorganization: Grouped the Core index by domain and moved function-go-templating readiness and external-query examples under a dedicated patterns index.

2026-07-14

  • Creation: Added manual composed-resource readiness patterns and a release-pinned Sveltos Profile-to-ClusterSummary ExtraResources example.

  • Creation: Added release-pinned EnvironmentConfig knowledge covering the retained Beta API, the v1.18 removal of native Composition integration, function-environment-configs v0.7.2 selection and merge behavior, and the environment-to-template-to-readiness pipeline.

  • Correction: Clarified from function-go-templating v0.12.2 conversion code and tests that ExtraResources matchLabels works for cluster-scoped resources; the defect is lost namespace scoping, which turns matchLabels plus namespace into an all-namespace list subject to RBAC.

  • Creation: Documented Crossplane's default composed-resource permission boundary, aggregated ClusterRole grant procedure, and RBAC-manager implications.

  • Update: Clarified the one-way effects of deleting or narrowing a ManagedResourceActivationPolicy, the related report in issue #6984, and the dedicated MRAP page's missing explicit warning.

  • Update: Clarified with function and Crossplane Core implementation evidence that function-go-templating ExtraResources zero-match lookups are non-fatal and do not impose a minimum result count.

  • Creation: Documented Beta real-time composition watches, TTL-driven reconciliation, required-resource refresh boundaries, and six related issue reports with released-fix provenance.

  • Creation: Documented the Crossplane v2 namespaced-composition boundary reported in issue #6759 and compared provider-kubernetes, Reflector, and kubernetes-replicator synchronization patterns.

  • Creation: Added a provider-opentofu and function-go-templating pattern for external queries, including static Function credential limits in multi-tenant pipelines.

  • Update: Added the Management Policies GA tracker, grouped known limitation reports, and selected-release containment for implemented policy combinations.

  • Update: Expanded function-go-templating issue #579 with its version scope, reported failure mode, proposed workarounds, and unresolved current-release applicability.

  • Creation: Documented the absence of native Composition health status and the evidence boundaries of Argo CD Lua and Flux CEL health customizations.

  • Creation: Added Crossplane Core Usage and ClusterUsage deletion protection, scope semantics, and current mixed namespace/cluster limitations.

  • Creation: Added a release-pinned function-auto-ready v0.7.0 knowledge set covering package use, readiness ordering, Kubernetes health checks, Beta input, and Alpha CEL customizations.

  • Creation: Added the Crossplane v2 function-go-templating pattern for aggregating observed connection details into an explicitly composed Kubernetes Secret.

  • Update: Documented function-go-templating Context semantics and the Crossplane v2 compatibility boundary of all special meta kinds.

  • Update: Documented exact function-go-templating helper semantics and added a dedicated ExtraResources capability reference.

2026-07-12

  • Update: Expanded provider-agnostic Managed Resource knowledge with anatomy, reconciliation lifecycle, policies, identity safety, references, ProviderConfig, controls, conditions, and MR activation APIs.

  • Creation: Added the two-role Crossplane Functions model, distinguishing composition functions from Alpha operation functions and documenting direct, scheduled, and watched invocation.

  • Creation: Added a v2.3.3-pinned summary of the Composition Functions specification, explicitly separated from operation functions.

  • Creation: Added Crossplane Configuration package concepts covering package contents, installation, revisions, dependencies, and authoring metadata.

  • Creation: Established a Crossplane Core v2.3.3 foundation covering composite resources, XRDs, Composition pipelines, managed resources, and MRDs.

  • Creation: Added a legacy-free, release-pinned function-go-templating v0.12.2 knowledge set with schema, behavior, helper, Sprig, and project-history concepts.

242 files

Advantages

  • Provides version-aware knowledge by linking facts to specific repository revisions. evidence: README.md
  • Connects distributed sources like Go APIs, CRDs, and documentation into a single navigable catalog. evidence: README.md

Limitations

  • The public MCP server is provided as an early-access service and is not intended for production use without self-hosting. evidence: README.md
  • Requires explicit provider versions for CRD tools, as it does not guess or infer versions automatically. evidence: README.md

Security

Risk level: Low risk

This brain runs

Agent instructions that run or fetch something (26)

  • .agents/agents/okf-function-go-templating-researcher/AGENT.md: Write for Crossplane users who want to install and use `function-go-templating` in Compositions.
  • .agents/agents/okf-reviewer/AGENT.md: `mise run lint` succeeds after the final fixes and before the root or parent agent creates a commit.
  • .agents/agents/okf-reviewer/AGENT.md: Run `mise run lint` as the final validation command.
  • .agents/skills/okf-open-knowledge-format/SKILL.md: If the user agrees to install:
  • .agents/skills/okf-open-knowledge-format/SKILL.md: uv tool install okflint
  • .agents/skills/okf-open-knowledge-format/SKILL.md: pip install okflint
  • .agents/skills/okf-open-knowledge-format/SKILL.md: kcmd push --dry-run
  • .agents/skills/okf-updates/SKILL.md: Run this workflow only after the user explicitly invokes `$okf-updates`, `/skill:okf-updates`, or `/okf-updates`.
  • .agents/skills/okf-updates/SKILL.md: Run at most three direct researchers at once.
  • .agents/skills/okf-updates/SKILL.md: A requester reply that selects one or more candidate IDs from this explicitly invoked workflow is explicit permission to run the normal OKF update logic for those candidates.
  • .agents/skills/okf-updates/SKILL.md: Run deterministic validation, `okf-reviewer`, and `mise run lint`.
  • .agents/skills/okf/SKILL.md: Run this workflow only after the user explicitly invokes `$okf`, `/skill:okf`, or `/okf`.
  • .agents/skills/okf/SKILL.md: After all review fixes, run `mise run lint`.
  • .agents/skills/okf/SKILL.md: Commit every intended file only after reviewer approval and a successful lint run.
  • .agents/skills/okf/SKILL.md: Run the Core docs and Core code researchers together when a concept needs both user-facing guidance and exact served API shape.
  • .agents/skills/okf/SKILL.md: Run independent read-heavy research in parallel, with at most three direct agents.
  • .agents/skills/okf/SKILL.md: After all fixes, run `mise run lint` and fix every reported issue.
  • .agents/skills/okf/SKILL.md: The reviewer may return `APPROVED` only after the final lint run succeeds.
  • .agents/skills/okf/SKILL.md: Non-thinking coding models such as Qwen3-Coder-Next can run every project agent without incompatible reasoning controls.
  • .agents/skills/okf/SKILL.md: deterministic validation and `mise run lint` results
  • AGENTS.md: Run the normal workflow only when the user explicitly invokes `$okf`, `/skill:okf`, or `/okf`, or selects a feature candidate returned by an explicitly invoked `$okf-updates`, `/skill:okf-updates`, or `/okf-updates` workflow.
  • AGENTS.md: Run update discovery only when the user explicitly invokes `$okf-updates`, `/skill:okf-updates`, or `/okf-updates`.
  • AGENTS.md: Run deterministic validation and the `okf-reviewer` before committing the changes.
  • AGENTS.md: After the final review fixes, run `mise run lint` before creating any commit.
  • AGENTS.md: After reviewer approval and a successful lint run, commit every intended change.
  • AGENTS.md: Create commits with a Developer Certificate of Origin sign-off by default by using `git commit --signoff` (or `git commit -s`).

MCP servers (1)

  • .mcp.json (crossplane-v2-okf): https://crossplane.mcp.jkroepke.de/mcp · uses the network
  • Low risk: network-instructions (.agents/skills/okf-open-knowledge-format/SKILL.md:214)

Attribution and licence

First committed by
GitHub avatar of jkroepkejkroepke
Publisher
Jan-Otto Kröpke (Community)
Source
jkroepke/okf-crossplane-v2 · commit df24ac2
Licence
Apache License 2.0 (files served here)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
jkroepke

AutoGineer is not affiliated with or endorsed by jkroepke.

Download

The ZIP holds the files AutoGineer serves, with ATTRIBUTION.md and the licence. Download okf-crossplane-v2.zip