Skip to content

Add AGENTS.md guidance for cross-file impact when Konflux PRs substitute Tekton tasks #3531

Description

@fullsend-ai-retro

What happened

PR #3513 was an automated Konflux/MintMaker PR updating 15 Tekton task bundle references. Most were routine digest or version bumps, but one change substituted the clair-scan task entirely with roxctl-scan — changing both the task name and bundle reference. The review agent on its second run (Aug 29, cost $3.52, claude-opus-4-6/high effort) correctly identified stale references to clair-scan in benchmark/offliner/scans.go:90 and hack/view-clair-reports.sh:39, neither of which were in the PR diff. The human confirmed the findings and filed follow-up PR #3530 for the benchmark offliner. The hack/view-clair-reports.sh stale reference remains unaddressed since the script is rarely used and the roxctl output format differs.

What could go better

The review agent caught the cross-file impact correctly on this PR, so this proposal is preventive rather than corrective. AGENTS.md currently has no guidance distinguishing routine Tekton bundle digest/version bumps from task substitutions (name changes). Task substitutions carry qualitatively different risk because they can silently break Go code, shell scripts, and tooling that filter by task name — producing empty results rather than errors. Without explicit guidance, detection depends on the agent's general reasoning rather than repo-specific knowledge of where task names are referenced (e.g., benchmark/offliner/, hack/, cmd/). Confidence: moderate — the agent already caught this correctly, but codifying the expectation makes the behavior more reliable across model versions and helps human reviewers recognize the risk pattern when triaging automated Konflux PRs.

Proposed change

Add a subsection to AGENTS.md (in the review guidance or CI/pipeline area) documenting the distinction between Tekton task bundle update types for Konflux/MintMaker PRs:

  1. Digest-only bumps and patch version bumps are low-risk — the task name and interface are unchanged, so cross-file analysis is unnecessary.
  2. Task name changes or task substitutions (e.g., clair-scanroxctl-scan) are higher-risk — the reviewer should grep the codebase for references to the old task name in Go source (benchmark/, cmd/), shell scripts (hack/), and documentation. These references often use string literals for task-name filtering in SLSA provenance attestations and will silently return empty results after the rename.
  3. When stale references are found, distinguish production code paths (higher priority) from developer utility scripts in hack/ (lower priority, per the conventions in issue Add AGENTS.md guidance for hack/ directory script conventions and review expectations #3508).

Validation criteria

On the next automated Konflux/MintMaker PR that contains a Tekton task name change (not just a digest or version bump), the review agent should flag cross-file stale references and cite the AGENTS.md guidance. Measure over the next 3 such PRs — each should include explicit cross-file analysis in the review findings when a task substitution is detected.


Generated by retro agent from #3513

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions