{"owner":"tektoncd","repo":"pipeline","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1782,"categories":["root-instruction","anthropic-skill","subagent-persona","plugin-manifest"],"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md","skills/tekton-pipeline-discovery/SKILL.md","docs/agents/agent-context.md","vendor/github.com/google/gnostic-models/extensions/README.md"],"skills":{"AGENTS.md":"# Agent notes for Tekton Pipelines\n\nIf you're an agent working in this repo, start here. This file is meant to orient you quickly; it does not replace the project docs or maintainer judgment.\n\n## Ground rules\n\n- These notes apply to the whole repo.\n- Do not add more `AGENTS.md` files unless a maintainer asks.\n- Keep changes narrow and easy to review.\n- Prefer the smallest test that proves the change.\n- Do not hand-edit generated files or `vendor/`; use the matching update script or dependency workflow.\n- When in doubt, follow nearby code and ask before inventing a new pattern.\n\n## Repo shape\n\n- `cmd/`: binaries such as controller, webhook, entrypoint, resolver, and events.\n- `pkg/apis/`: API types, defaults, validation, conversion, and generated clients.\n- `pkg/reconciler/`: TaskRun, PipelineRun, CustomRun, resolver, event, and notification reconcilers.\n- `pkg/pod`, `pkg/workspace`, `pkg/substitution`: helpers used by the reconcilers.\n- `internal/`: private implementation packages; prefer this for new non-API helpers.\n- `config/`: install manifests and CRDs. Many files here are generated.\n- `test/`: e2e tests, conformance tests, helpers, and presubmit scripts.\n- `docs/`: user-facing and developer documentation.\n\n## Before changing code\n\n- Read `CONTRIBUTING.md`, `DEVELOPMENT.md`, `test/README.md`, and the docs for the area you are touching.\n- When opening PRs, follow the repo's PR template in `.github/pull_request_template.md`.\n- For API changes, read `api_compatibility_policy.md` first and expect codegen/OpenAPI updates.\n- For reconciler changes, add or update package tests with fake clients before reaching for e2e tests.\n- For e2e changes, follow the annotations and categories in `test/README.md`.\n\n## Useful checks\n\n- Format Go: `gofmt -w <files>`.\n- Test one package: `go test ./path/to/package`.\n- Test one case: `go test ./path/to/package -run TestName`.\n- Run common packages: `go test ./pkg/...`.\n- Run generated-code check: `./hack/verify-codegen.sh`.\n- Update generated code when needed: `./hack/update-codegen.sh`.\n- Run the local agent-context check: `./hack/verify-agent-readiness.sh`.\n\n## More context\n\n- Repo map for agents: `docs/agents/agent-context.md`.\n- Discovery skill: `skills/tekton-pipeline-discovery/SKILL.md`.\n- Skill discovery symlinks live under `.agents/`, `.claude/`, `.codex/`, and `.cursor/`.\n","skills/tekton-pipeline-discovery/SKILL.md":"---\nname: tekton-pipeline-discovery\ndescription: Use this when you need to find your way around tektoncd/pipeline before editing, reviewing, or debugging Tekton Pipelines code.\n---\n\n# Tekton Pipeline Discovery\n\nUse this skill for the first pass through the repo. It should help you find the right files quickly without turning into a second set of project rules.\n\n## Start here\n\n1. Read `AGENTS.md`.\n2. Use `docs/agents/agent-context.md` as the repo map.\n3. Then read the docs for the area you are touching. The common ones are `CONTRIBUTING.md`, `DEVELOPMENT.md`, `api_compatibility_policy.md`, `test/README.md`, and files under `docs/developers/`.\n\n## Working notes\n\n- Keep the change small enough that a maintainer can review it without guessing your intent.\n- Test the package you touched before running broad suites.\n- Prefer new private helpers under `internal/` unless the code is intentionally public API.\n- Do not hand-edit generated code or `vendor/`.\n- For CRD/API behavior, check compatibility before changing fields, defaults, status, labels, or generated clients.\n- For e2e changes, follow the categories and annotations in `test/README.md`.\n\n## Common commands\n\n```sh\ngo test ./pkg/...                         # broad package tests\n./hack/verify-codegen.sh                  # generated-code consistency\n./hack/verify-agent-readiness.sh          # local AGENTS.md and skill discovery check\n```\n\n## PR notes\n\n- Follow `.github/pull_request_template.md`.\n- Keep the `release-note` block accurate; use `NONE` only when there is no user-facing impact.\n- Use `Fixes #...` only when the PR fully resolves the issue.\n- For agent-context-only docs changes, `./hack/verify-agent-readiness.sh` is usually the right targeted check.\n","docs/agents/agent-context.md":"# Tekton Pipelines repo map for agents\n\nUse this as a map after you read `AGENTS.md`. It points you toward the right code and docs; it is not another rule file.\n\nThe source-of-truth docs are still `README.md`, `CONTRIBUTING.md`, `DEVELOPMENT.md`, `api_compatibility_policy.md`, and `test/README.md`.\n\n## What this repo does\n\nTekton Pipelines defines Kubernetes-native CI/CD APIs and the controllers that run them. The main resources are `Task`, `TaskRun`, `Pipeline`, `PipelineRun`, `CustomRun`, and resolver objects. The main binaries are the controller, webhook, entrypoint, events controller, remote resolvers, and small helper images.\n\n## Runtime path\n\n1. A user creates Tekton resources through the Kubernetes API.\n2. Webhooks default, validate, and convert those resources.\n3. Reconcilers watch resources through generated informers.\n4. TaskRun reconciliation builds Pods and entrypoint config.\n5. PipelineRun reconciliation resolves the graph and creates child runs.\n6. Resolver controllers fetch remote task and pipeline definitions.\n7. Event and notification controllers publish run state changes.\n\n## Where to look\n\n| Path | Use it for |\n| --- | --- |\n| `cmd/controller` | Controller binary setup and reconciler wiring. |\n| `cmd/webhook` | Defaulting, validation, and conversion webhooks. |\n| `cmd/entrypoint` | The process wrapper injected into step containers. |\n| `pkg/apis/pipeline` | API types, defaults, validation, and conversions. |\n| `pkg/client` | Generated clients, listers, informers, and reconcilers. |\n| `pkg/reconciler/taskrun` | TaskRun reconciliation, Pod creation, and TaskRun status. |\n| `pkg/reconciler/pipelinerun` | PipelineRun graph resolution and child run orchestration. |\n| `pkg/reconciler/resolution` | Remote resolution request handling. |\n| `pkg/reconciler/events`, `pkg/reconciler/notifications` | CloudEvents and notification controllers. |\n| `pkg/pod` | Pod and entrypoint construction helpers. |\n| `internal` | Private helpers. Prefer this for new non-API packages. |\n| `config` | Install manifests and CRDs. |\n| `test` | E2E, conformance, and test utilities. |\n| `hack` | Codegen, verification, release, and local-cluster scripts. |\n| `skills/tekton-pipeline-discovery` | Repo-specific discovery skill for agents. |\n\n## Common change paths\n\n- API or CRD changes: read `api_compatibility_policy.md`; run the generated-code and OpenAPI updates.\n- Webhook changes: add or update validation/defaulting/conversion tests under `pkg/apis/...`.\n- Reconciler changes: start with fake-client unit tests; add e2e coverage when behavior changes across controllers or Pods.\n- Generated files: run the matching `hack/update-*` script instead of editing generated output by hand.\n- E2E tests: keep `@test:execution=parallel` or `serial` annotations correct.\n\n## Useful targeted checks\n\n```sh\n./hack/verify-agent-readiness.sh\ngo test ./pkg/apis/pipeline/v1 ./pkg/apis/pipeline/v1beta1\ngo test ./pkg/reconciler/taskrun ./pkg/reconciler/pipelinerun\n./hack/verify-codegen.sh\n```\n\nStart narrow. Broaden the test run only when the touched area needs it.\n","vendor/github.com/google/gnostic-models/extensions/README.md":"# Extensions\n\n**Extension Support is experimental.**\n\nThis directory contains support code for building Gnostic extensio handlers and\nassociated examples.\n\nExtension handlers can be used to compile vendor or specification extensions\ninto protocol buffer structures.\n\nLike plugins, extension handlers are built as separate executables. Extension\nbodies are written to extension handlers as serialized\nExtensionHandlerRequests.\n"},"files":{"AGENTS.md":"# Agent notes for Tekton Pipelines\n\nIf you're an agent working in this repo, start here. This file is meant to orient you quickly; it does not replace the project docs or maintainer judgment.\n\n## Ground rules\n\n- These notes apply to the whole repo.\n- Do not add more `AGENTS.md` files unless a maintainer asks.\n- Keep changes narrow and easy to review.\n- Prefer the smallest test that proves the change.\n- Do not hand-edit generated files or `vendor/`; use the matching update script or dependency workflow.\n- When in doubt, follow nearby code and ask before inventing a new pattern.\n\n## Repo shape\n\n- `cmd/`: binaries such as controller, webhook, entrypoint, resolver, and events.\n- `pkg/apis/`: API types, defaults, validation, conversion, and generated clients.\n- `pkg/reconciler/`: TaskRun, PipelineRun, CustomRun, resolver, event, and notification reconcilers.\n- `pkg/pod`, `pkg/workspace`, `pkg/substitution`: helpers used by the reconcilers.\n- `internal/`: private implementation packages; prefer this for new non-API helpers.\n- `config/`: install manifests and CRDs. Many files here are generated.\n- `test/`: e2e tests, conformance tests, helpers, and presubmit scripts.\n- `docs/`: user-facing and developer documentation.\n\n## Before changing code\n\n- Read `CONTRIBUTING.md`, `DEVELOPMENT.md`, `test/README.md`, and the docs for the area you are touching.\n- When opening PRs, follow the repo's PR template in `.github/pull_request_template.md`.\n- For API changes, read `api_compatibility_policy.md` first and expect codegen/OpenAPI updates.\n- For reconciler changes, add or update package tests with fake clients before reaching for e2e tests.\n- For e2e changes, follow the annotations and categories in `test/README.md`.\n\n## Useful checks\n\n- Format Go: `gofmt -w <files>`.\n- Test one package: `go test ./path/to/package`.\n- Test one case: `go test ./path/to/package -run TestName`.\n- Run common packages: `go test ./pkg/...`.\n- Run generated-code check: `./hack/verify-codegen.sh`.\n- Update generated code when needed: `./hack/update-codegen.sh`.\n- Run the local agent-context check: `./hack/verify-agent-readiness.sh`.\n\n## More context\n\n- Repo map for agents: `docs/agents/agent-context.md`.\n- Discovery skill: `skills/tekton-pipeline-discovery/SKILL.md`.\n- Skill discovery symlinks live under `.agents/`, `.claude/`, `.codex/`, and `.cursor/`.\n","skills/tekton-pipeline-discovery/SKILL.md":"---\nname: tekton-pipeline-discovery\ndescription: Use this when you need to find your way around tektoncd/pipeline before editing, reviewing, or debugging Tekton Pipelines code.\n---\n\n# Tekton Pipeline Discovery\n\nUse this skill for the first pass through the repo. It should help you find the right files quickly without turning into a second set of project rules.\n\n## Start here\n\n1. Read `AGENTS.md`.\n2. Use `docs/agents/agent-context.md` as the repo map.\n3. Then read the docs for the area you are touching. The common ones are `CONTRIBUTING.md`, `DEVELOPMENT.md`, `api_compatibility_policy.md`, `test/README.md`, and files under `docs/developers/`.\n\n## Working notes\n\n- Keep the change small enough that a maintainer can review it without guessing your intent.\n- Test the package you touched before running broad suites.\n- Prefer new private helpers under `internal/` unless the code is intentionally public API.\n- Do not hand-edit generated code or `vendor/`.\n- For CRD/API behavior, check compatibility before changing fields, defaults, status, labels, or generated clients.\n- For e2e changes, follow the categories and annotations in `test/README.md`.\n\n## Common commands\n\n```sh\ngo test ./pkg/...                         # broad package tests\n./hack/verify-codegen.sh                  # generated-code consistency\n./hack/verify-agent-readiness.sh          # local AGENTS.md and skill discovery check\n```\n\n## PR notes\n\n- Follow `.github/pull_request_template.md`.\n- Keep the `release-note` block accurate; use `NONE` only when there is no user-facing impact.\n- Use `Fixes #...` only when the PR fully resolves the issue.\n- For agent-context-only docs changes, `./hack/verify-agent-readiness.sh` is usually the right targeted check.\n","docs/agents/agent-context.md":"# Tekton Pipelines repo map for agents\n\nUse this as a map after you read `AGENTS.md`. It points you toward the right code and docs; it is not another rule file.\n\nThe source-of-truth docs are still `README.md`, `CONTRIBUTING.md`, `DEVELOPMENT.md`, `api_compatibility_policy.md`, and `test/README.md`.\n\n## What this repo does\n\nTekton Pipelines defines Kubernetes-native CI/CD APIs and the controllers that run them. The main resources are `Task`, `TaskRun`, `Pipeline`, `PipelineRun`, `CustomRun`, and resolver objects. The main binaries are the controller, webhook, entrypoint, events controller, remote resolvers, and small helper images.\n\n## Runtime path\n\n1. A user creates Tekton resources through the Kubernetes API.\n2. Webhooks default, validate, and convert those resources.\n3. Reconcilers watch resources through generated informers.\n4. TaskRun reconciliation builds Pods and entrypoint config.\n5. PipelineRun reconciliation resolves the graph and creates child runs.\n6. Resolver controllers fetch remote task and pipeline definitions.\n7. Event and notification controllers publish run state changes.\n\n## Where to look\n\n| Path | Use it for |\n| --- | --- |\n| `cmd/controller` | Controller binary setup and reconciler wiring. |\n| `cmd/webhook` | Defaulting, validation, and conversion webhooks. |\n| `cmd/entrypoint` | The process wrapper injected into step containers. |\n| `pkg/apis/pipeline` | API types, defaults, validation, and conversions. |\n| `pkg/client` | Generated clients, listers, informers, and reconcilers. |\n| `pkg/reconciler/taskrun` | TaskRun reconciliation, Pod creation, and TaskRun status. |\n| `pkg/reconciler/pipelinerun` | PipelineRun graph resolution and child run orchestration. |\n| `pkg/reconciler/resolution` | Remote resolution request handling. |\n| `pkg/reconciler/events`, `pkg/reconciler/notifications` | CloudEvents and notification controllers. |\n| `pkg/pod` | Pod and entrypoint construction helpers. |\n| `internal` | Private helpers. Prefer this for new non-API packages. |\n| `config` | Install manifests and CRDs. |\n| `test` | E2E, conformance, and test utilities. |\n| `hack` | Codegen, verification, release, and local-cluster scripts. |\n| `skills/tekton-pipeline-discovery` | Repo-specific discovery skill for agents. |\n\n## Common change paths\n\n- API or CRD changes: read `api_compatibility_policy.md`; run the generated-code and OpenAPI updates.\n- Webhook changes: add or update validation/defaulting/conversion tests under `pkg/apis/...`.\n- Reconciler changes: start with fake-client unit tests; add e2e coverage when behavior changes across controllers or Pods.\n- Generated files: run the matching `hack/update-*` script instead of editing generated output by hand.\n- E2E tests: keep `@test:execution=parallel` or `serial` annotations correct.\n\n## Useful targeted checks\n\n```sh\n./hack/verify-agent-readiness.sh\ngo test ./pkg/apis/pipeline/v1 ./pkg/apis/pipeline/v1beta1\ngo test ./pkg/reconciler/taskrun ./pkg/reconciler/pipelinerun\n./hack/verify-codegen.sh\n```\n\nStart narrow. Broaden the test run only when the touched area needs it.\n","vendor/github.com/google/gnostic-models/extensions/README.md":"# Extensions\n\n**Extension Support is experimental.**\n\nThis directory contains support code for building Gnostic extensio handlers and\nassociated examples.\n\nExtension handlers can be used to compile vendor or specification extensions\ninto protocol buffer structures.\n\nLike plugins, extension handlers are built as separate executables. Extension\nbodies are written to extension handlers as serialized\nExtensionHandlerRequests.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/tektoncd/pipeline/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# Agent notes for Tekton Pipelines\n\nIf you're an agent working in this repo, start here. This file is meant to orient you quickly; it does not replace the project docs or maintainer judgment.\n\n## Ground rules\n\n- These notes apply to the whole repo.\n- Do not add more `AGENTS.md` files unless a maintainer asks.\n- Keep changes narrow and easy to review.\n- Prefer the smallest test that proves the change.\n- Do not hand-edit generated files or `vendor/`; use the matching update script or dependency workflow.\n- When in doubt, follow nearby code and ask before inventing a new pattern.\n\n## Repo shape\n\n- `cmd/`: binaries such as controller, webhook, entrypoint, resolver, and events.\n- `pkg/apis/`: API types, defaults, validation, conversion, and generated clients.\n- `pkg/reconciler/`: TaskRun, PipelineRun, CustomRun, resolver, event, and notification reconcilers.\n- `pkg/pod`, `pkg/workspace`, `pkg/substitution`: helpers used by the reconcilers.\n- `internal/`: private implementation packages; prefer this for new non-API helpers.\n- `config/`: install manifests and CRDs. Many files here are generated.\n- `test/`: e2e tests, conformance tests, helpers, and presubmit scripts.\n- `docs/`: user-facing and developer documentation.\n\n## Before changing code\n\n- Read `CONTRIBUTING.md`, `DEVELOPMENT.md`, `test/README.md`, and the docs for the area you are touching.\n- When opening PRs, follow the repo's PR template in `.github/pull_request_template.md`.\n- For API changes, read `api_compatibility_policy.md` first and expect codegen/OpenAPI updates.\n- For reconciler changes, add or update package tests with fake clients before reaching for e2e tests.\n- For e2e changes, follow the annotations and categories in `test/README.md`.\n\n## Useful checks\n\n- Format Go: `gofmt -w <files>`.\n- Test one package: `go test ./path/to/package`.\n- Test one case: `go test ./path/to/package -run TestName`.\n- Run common packages: `go test ./pkg/...`.\n- Run generated-code check: `./hack/verify-codegen.sh`.\n- Update generated code when needed: `./hack/update-codegen.sh`.\n- Run the local agent-context check: `./hack/verify-agent-readiness.sh`.\n\n## More context\n\n- Repo map for agents: `docs/agents/agent-context.md`.\n- Discovery skill: `skills/tekton-pipeline-discovery/SKILL.md`.\n- Skill discovery symlinks live under `.agents/`, `.claude/`, `.codex/`, and `.cursor/`.\n","isInternal":false,"tokens":581,"sizeBytes":2354},{"name":"SKILL.md","path":"skills/tekton-pipeline-discovery/SKILL.md","rawUrl":"https://raw.githubusercontent.com/tektoncd/pipeline/HEAD/skills/tekton-pipeline-discovery/SKILL.md","title":"tekton-pipeline-discovery","category":"anthropic-skill","format":"markdown","content":"---\nname: tekton-pipeline-discovery\ndescription: Use this when you need to find your way around tektoncd/pipeline before editing, reviewing, or debugging Tekton Pipelines code.\n---\n\n# Tekton Pipeline Discovery\n\nUse this skill for the first pass through the repo. It should help you find the right files quickly without turning into a second set of project rules.\n\n## Start here\n\n1. Read `AGENTS.md`.\n2. Use `docs/agents/agent-context.md` as the repo map.\n3. Then read the docs for the area you are touching. The common ones are `CONTRIBUTING.md`, `DEVELOPMENT.md`, `api_compatibility_policy.md`, `test/README.md`, and files under `docs/developers/`.\n\n## Working notes\n\n- Keep the change small enough that a maintainer can review it without guessing your intent.\n- Test the package you touched before running broad suites.\n- Prefer new private helpers under `internal/` unless the code is intentionally public API.\n- Do not hand-edit generated code or `vendor/`.\n- For CRD/API behavior, check compatibility before changing fields, defaults, status, labels, or generated clients.\n- For e2e changes, follow the categories and annotations in `test/README.md`.\n\n## Common commands\n\n```sh\ngo test ./pkg/...                         # broad package tests\n./hack/verify-codegen.sh                  # generated-code consistency\n./hack/verify-agent-readiness.sh          # local AGENTS.md and skill discovery check\n```\n\n## PR notes\n\n- Follow `.github/pull_request_template.md`.\n- Keep the `release-note` block accurate; use `NONE` only when there is no user-facing impact.\n- Use `Fixes #...` only when the PR fully resolves the issue.\n- For agent-context-only docs changes, `./hack/verify-agent-readiness.sh` is usually the right targeted check.\n","frontmatter":{"name":"tekton-pipeline-discovery","description":"Use this when you need to find your way around tektoncd/pipeline before editing, reviewing, or debugging Tekton Pipelines code."},"isInternal":false,"tokens":395,"sizeBytes":1735},{"name":"README.md","path":"vendor/github.com/google/gnostic-models/extensions/README.md","rawUrl":"https://raw.githubusercontent.com/tektoncd/pipeline/HEAD/vendor/github.com/google/gnostic-models/extensions/README.md","title":"extensions Documentation","category":"plugin-manifest","format":"markdown","content":"# Extensions\n\n**Extension Support is experimental.**\n\nThis directory contains support code for building Gnostic extensio handlers and\nassociated examples.\n\nExtension handlers can be used to compile vendor or specification extensions\ninto protocol buffer structures.\n\nLike plugins, extension handlers are built as separate executables. Extension\nbodies are written to extension handlers as serialized\nExtensionHandlerRequests.\n","isInternal":false,"tokens":73,"sizeBytes":426},{"name":"agent-context.md","path":"docs/agents/agent-context.md","rawUrl":"https://raw.githubusercontent.com/tektoncd/pipeline/HEAD/docs/agents/agent-context.md","title":"Subagent: agent-context","category":"subagent-persona","format":"markdown","content":"# Tekton Pipelines repo map for agents\n\nUse this as a map after you read `AGENTS.md`. It points you toward the right code and docs; it is not another rule file.\n\nThe source-of-truth docs are still `README.md`, `CONTRIBUTING.md`, `DEVELOPMENT.md`, `api_compatibility_policy.md`, and `test/README.md`.\n\n## What this repo does\n\nTekton Pipelines defines Kubernetes-native CI/CD APIs and the controllers that run them. The main resources are `Task`, `TaskRun`, `Pipeline`, `PipelineRun`, `CustomRun`, and resolver objects. The main binaries are the controller, webhook, entrypoint, events controller, remote resolvers, and small helper images.\n\n## Runtime path\n\n1. A user creates Tekton resources through the Kubernetes API.\n2. Webhooks default, validate, and convert those resources.\n3. Reconcilers watch resources through generated informers.\n4. TaskRun reconciliation builds Pods and entrypoint config.\n5. PipelineRun reconciliation resolves the graph and creates child runs.\n6. Resolver controllers fetch remote task and pipeline definitions.\n7. Event and notification controllers publish run state changes.\n\n## Where to look\n\n| Path | Use it for |\n| --- | --- |\n| `cmd/controller` | Controller binary setup and reconciler wiring. |\n| `cmd/webhook` | Defaulting, validation, and conversion webhooks. |\n| `cmd/entrypoint` | The process wrapper injected into step containers. |\n| `pkg/apis/pipeline` | API types, defaults, validation, and conversions. |\n| `pkg/client` | Generated clients, listers, informers, and reconcilers. |\n| `pkg/reconciler/taskrun` | TaskRun reconciliation, Pod creation, and TaskRun status. |\n| `pkg/reconciler/pipelinerun` | PipelineRun graph resolution and child run orchestration. |\n| `pkg/reconciler/resolution` | Remote resolution request handling. |\n| `pkg/reconciler/events`, `pkg/reconciler/notifications` | CloudEvents and notification controllers. |\n| `pkg/pod` | Pod and entrypoint construction helpers. |\n| `internal` | Private helpers. Prefer this for new non-API packages. |\n| `config` | Install manifests and CRDs. |\n| `test` | E2E, conformance, and test utilities. |\n| `hack` | Codegen, verification, release, and local-cluster scripts. |\n| `skills/tekton-pipeline-discovery` | Repo-specific discovery skill for agents. |\n\n## Common change paths\n\n- API or CRD changes: read `api_compatibility_policy.md`; run the generated-code and OpenAPI updates.\n- Webhook changes: add or update validation/defaulting/conversion tests under `pkg/apis/...`.\n- Reconciler changes: start with fake-client unit tests; add e2e coverage when behavior changes across controllers or Pods.\n- Generated files: run the matching `hack/update-*` script instead of editing generated output by hand.\n- E2E tests: keep `@test:execution=parallel` or `serial` annotations correct.\n\n## Useful targeted checks\n\n```sh\n./hack/verify-agent-readiness.sh\ngo test ./pkg/apis/pipeline/v1 ./pkg/apis/pipeline/v1beta1\ngo test ./pkg/reconciler/taskrun ./pkg/reconciler/pipelinerun\n./hack/verify-codegen.sh\n```\n\nStart narrow. Broaden the test run only when the touched area needs it.\n","isInternal":false,"tokens":733,"sizeBytes":3077}],"systemPromptSnippet":"<yakaai_skills repo=\"tektoncd/pipeline\">\n<!-- File: AGENTS.md (Tokens: ~581 | Category: root-instruction) -->\n# Agent notes for Tekton Pipelines\n\nIf you're an agent working in this repo, start here. This file is meant to orient you quickly; it does not replace the project docs or maintainer judgment.\n\n## Ground rules\n\n- These notes apply to the whole repo.\n- Do not add more `AGENTS.md` files unless a maintainer asks.\n- Keep changes narrow and easy to review.\n- Prefer the smallest test that proves the change.\n- Do not hand-edit generated files or `vendor/`; use the matching update script or dependency workflow.\n- When in doubt, follow nearby code and ask before inventing a new pattern.\n\n## Repo shape\n\n- `cmd/`: binaries such as controller, webhook, entrypoint, resolver, and events.\n- `pkg/apis/`: API types, defaults, validation, conversion, and generated clients.\n- `pkg/reconciler/`: TaskRun, PipelineRun, CustomRun, resolver, event, and notification reconcilers.\n- `pkg/pod`, `pkg/workspace`, `pkg/substitution`: helpers used by the reconcilers.\n- `internal/`: private implementation packages; prefer this for new non-API helpers.\n- `config/`: install manifests and CRDs. Many files here are generated.\n- `test/`: e2e tests, conformance tests, helpers, and presubmit scripts.\n- `docs/`: user-facing and developer documentation.\n\n## Before changing code\n\n- Read `CONTRIBUTING.md`, `DEVELOPMENT.md`, `test/README.md`, and the docs for the area you are touching.\n- When opening PRs, follow the repo's PR template in `.github/pull_request_template.md`.\n- For API changes, read `api_compatibility_policy.md` first and expect codegen/OpenAPI updates.\n- For reconciler changes, add or update package tests with fake clients before reaching for e2e tests.\n- For e2e changes, follow the annotations and categories in `test/README.md`.\n\n## Useful checks\n\n- Format Go: `gofmt -w <files>`.\n- Test one package: `go test ./path/to/package`.\n- Test one case: `go test ./path/to/package -run TestName`.\n- Run common packages: `go test ./pkg/...`.\n- Run generated-code check: `./hack/verify-codegen.sh`.\n- Update generated code when needed: `./hack/update-codegen.sh`.\n- Run the local agent-context check: `./hack/verify-agent-readiness.sh`.\n\n## More context\n\n- Repo map for agents: `docs/agents/agent-context.md`.\n- Discovery skill: `skills/tekton-pipeline-discovery/SKILL.md`.\n- Skill discovery symlinks live under `.agents/`, `.claude/`, `.codex/`, and `.cursor/`.\n\n<!-- File: skills/tekton-pipeline-discovery/SKILL.md (Tokens: ~395 | Category: anthropic-skill) -->\n---\nname: tekton-pipeline-discovery\ndescription: Use this when you need to find your way around tektoncd/pipeline before editing, reviewing, or debugging Tekton Pipelines code.\n---\n\n# Tekton Pipeline Discovery\n\nUse this skill for the first pass through the repo. It should help you find the right files quickly without turning into a second set of project rules.\n\n## Start here\n\n1. Read `AGENTS.md`.\n2. Use `docs/agents/agent-context.md` as the repo map.\n3. Then read the docs for the area you are touching. The common ones are `CONTRIBUTING.md`, `DEVELOPMENT.md`, `api_compatibility_policy.md`, `test/README.md`, and files under `docs/developers/`.\n\n## Working notes\n\n- Keep the change small enough that a maintainer can review it without guessing your intent.\n- Test the package you touched before running broad suites.\n- Prefer new private helpers under `internal/` unless the code is intentionally public API.\n- Do not hand-edit generated code or `vendor/`.\n- For CRD/API behavior, check compatibility before changing fields, defaults, status, labels, or generated clients.\n- For e2e changes, follow the categories and annotations in `test/README.md`.\n\n## Common commands\n\n```sh\ngo test ./pkg/...                         # broad package tests\n./hack/verify-codegen.sh                  # generated-code consistency\n./hack/verify-agent-readiness.sh          # local AGENTS.md and skill discovery check\n```\n\n## PR notes\n\n- Follow `.github/pull_request_template.md`.\n- Keep the `release-note` block accurate; use `NONE` only when there is no user-facing impact.\n- Use `Fixes #...` only when the PR fully resolves the issue.\n- For agent-context-only docs changes, `./hack/verify-agent-readiness.sh` is usually the right targeted check.\n\n<!-- File: vendor/github.com/google/gnostic-models/extensions/README.md (Tokens: ~73 | Category: plugin-manifest) -->\n# Extensions\n\n**Extension Support is experimental.**\n\nThis directory contains support code for building Gnostic extensio handlers and\nassociated examples.\n\nExtension handlers can be used to compile vendor or specification extensions\ninto protocol buffer structures.\n\nLike plugins, extension handlers are built as separate executables. Extension\nbodies are written to extension handlers as serialized\nExtensionHandlerRequests.\n\n<!-- File: docs/agents/agent-context.md (Tokens: ~733 | Category: subagent-persona) -->\n# Tekton Pipelines repo map for agents\n\nUse this as a map after you read `AGENTS.md`. It points you toward the right code and docs; it is not another rule file.\n\nThe source-of-truth docs are still `README.md`, `CONTRIBUTING.md`, `DEVELOPMENT.md`, `api_compatibility_policy.md`, and `test/README.md`.\n\n## What this repo does\n\nTekton Pipelines defines Kubernetes-native CI/CD APIs and the controllers that run them. The main resources are `Task`, `TaskRun`, `Pipeline`, `PipelineRun`, `CustomRun`, and resolver objects. The main binaries are the controller, webhook, entrypoint, events controller, remote resolvers, and small helper images.\n\n## Runtime path\n\n1. A user creates Tekton resources through the Kubernetes API.\n2. Webhooks default, validate, and convert those resources.\n3. Reconcilers watch resources through generated informers.\n4. TaskRun reconciliation builds Pods and entrypoint config.\n5. PipelineRun reconciliation resolves the graph and creates child runs.\n6. Resolver controllers fetch remote task and pipeline definitions.\n7. Event and notification controllers publish run state changes.\n\n## Where to look\n\n| Path | Use it for |\n| --- | --- |\n| `cmd/controller` | Controller binary setup and reconciler wiring. |\n| `cmd/webhook` | Defaulting, validation, and conversion webhooks. |\n| `cmd/entrypoint` | The process wrapper injected into step containers. |\n| `pkg/apis/pipeline` | API types, defaults, validation, and conversions. |\n| `pkg/client` | Generated clients, listers, informers, and reconcilers. |\n| `pkg/reconciler/taskrun` | TaskRun reconciliation, Pod creation, and TaskRun status. |\n| `pkg/reconciler/pipelinerun` | PipelineRun graph resolution and child run orchestration. |\n| `pkg/reconciler/resolution` | Remote resolution request handling. |\n| `pkg/reconciler/events`, `pkg/reconciler/notifications` | CloudEvents and notification controllers. |\n| `pkg/pod` | Pod and entrypoint construction helpers. |\n| `internal` | Private helpers. Prefer this for new non-API packages. |\n| `config` | Install manifests and CRDs. |\n| `test` | E2E, conformance, and test utilities. |\n| `hack` | Codegen, verification, release, and local-cluster scripts. |\n| `skills/tekton-pipeline-discovery` | Repo-specific discovery skill for agents. |\n\n## Common change paths\n\n- API or CRD changes: read `api_compatibility_policy.md`; run the generated-code and OpenAPI updates.\n- Webhook changes: add or update validation/defaulting/conversion tests under `pkg/apis/...`.\n- Reconciler changes: start with fake-client unit tests; add e2e coverage when behavior changes across controllers or Pods.\n- Generated files: run the matching `hack/update-*` script instead of editing generated output by hand.\n- E2E tests: keep `@test:execution=parallel` or `serial` annotations correct.\n\n## Useful targeted checks\n\n```sh\n./hack/verify-agent-readiness.sh\ngo test ./pkg/apis/pipeline/v1 ./pkg/apis/pipeline/v1beta1\ngo test ./pkg/reconciler/taskrun ./pkg/reconciler/pipelinerun\n./hack/verify-codegen.sh\n```\n\nStart narrow. Broaden the test run only when the touched area needs it.\n</yakaai_skills>"}