Uh oh!
There was an error while loading. Please reload this page.
Closed
Add task-preflight skill to stop zero-diff retry PRs on container-vuln and refactor tasks#53674
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
CopilotAI
changed the title
[WIP] Fix zero-diff retries on container vulnerability and refactor tasksAdd task-preflight skill to stop zero-diff retry PRs on container-vuln and refactor tasksAug 18, 2026
Contributor
PR TriageCategory: chore (WIP) | Risk: low | Priority: low (score 20)
Recommended action: defer — recheck once agent finishes and diff is populated
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Container-vulnerability-fix and large-refactor tasks repeatedly burned full agent sessions: 5 of 6 closed PRs across three topics had 0 additions/0 deletions and no comments, so each retry restarted from zero with no record of the blocker.
Changes
.github/skills/task-preflight/SKILL.md(new) — feasibility check that must pass before any code is pushed, covering the two topics that produce zero-diff PRs:gh aw compile --force-refresh-container-pins --syft --grype --grant; unreachable image ⇒ blocker report. Otherwise route to one of the two real remediations — refresh the pin (commit changed.lock.yml) or add a scoped.grype.yamlignore entry with areason. Stale finding ⇒ report with scan output, no PR.make golint-custom(largefunc, 60-line default) instead of guessing, scope to a small named subset with a written extraction plan, keep it behaviour-preserving. Repo-wide rewrites like the 6096/6203-line attempt in#49825are explicitly out.AGENTS.md— one routing line in "Use these skills by intent", keeping the ambient file short per the repo's lazy-loading policy.Blocker report shape the skill prescribes:
Notes
The issue asks for a plan comment on the issue before opening a PR. No issue-comment tool was available in this environment, so the plan and links to the six prior closed PRs were published in the PR description before any content changes were pushed.