Use with the retro agent when deciding whether workflow observations are actionable proposals. Filters process-only noise and deduplicates proposals by root cause while preserving concrete production, security, CI, and recurring contributor failures.
Create a test plan for a PROJQUAY JIRA ticket, validate it with the user, then execute each scenario as manual verification. Covers acceptance criteria, real-user workflows, edge cases, and cross-feature regression.
Force short user-facing triage comments and retro summaries. Keep structured JSON and proposal evidence complete. Ban filler, hedging, and repetition.
Systematically rebase a branch onto its upstream target. Use when a feature branch has fallen behind, needs conflict resolution, requires commit cleanup before merge, or when a PR review requests a rebase. Handles complex multi-commit branches with many…
Reference for using the acli (Atlassian CLI) to interact with JIRA issues. Covers searching with JQL, creating, viewing, editing, transitioning, assigning, commenting, linking, cloning, and bulk operations. Use when performing any JIRA issue operation via…
Use when user asks about Konflux concepts, resources, pipelines, builds, releases, integration testing, Enterprise Contract, or troubleshooting Konflux issues. Triggers on any Konflux-related question or problem.
Generic CVE triage: fetch advisories (NVD, GHSA, Go vuln DB), check package presence in dependency manifests, classify verdict, write assessment artifact, and post Jira comment. Project workflows supply repo mapping and branch policy.
Apply a Go dependency CVE fix: go get, go mod tidy, verify with govulncheck.