fix-security-issue

Automating security remediation involves processing GitHub issues labeled topic:security and state:agent-ready, extracting the approved plan from security-review-agent comments, applying code edits, running tests, and opening a verification PR.

Patching a vulnerability requires a GitHub issue labeled state:agent-ready and topic:security, alongside a security-review-agent comment containing a legitimate concern and a concrete remediation plan to execute.

An agent implements a security fix by orchestrating workflow steps from plan extraction to branch creation, applying validated code changes, updating documentation, executing tests, and submitting a pull request.

Yes, automated vulnerability patching can be triggered using configurable keywords such as fix security issue, remediate security, implement security fix, and patch vulnerability to start the workflow.

No, the agent will not process a security issue without a remediation plan; it requires a security-review-agent comment confirming a legitimate concern and providing a concrete plan before initiating any code changes.