Add security alert burndown campaign with clustering and Claude codegen #10623
+6,253
−186
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.
Implements a campaign to systematically eliminate code security alerts, prioritizing file write vulnerabilities with intelligent clustering (up to 3 related alerts per fix) and comprehensive inline documentation.
Architecture
Campaign Specification (
security-alert-burndown.campaign.md)Worker Workflow (
security-alert-cluster-fixer.md)file-write,path-injection,tainted-pathvulnerabilitiesOrchestrator (
security-alert-burndown-orchestrator.md)Clustering Strategy
Reduces PR volume while maintaining context:
Code Comments
All fixes include security context:
Dual Engine Rationale
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.