# Remediations ## Overview Nullify drafts production-ready fixes for all finding types: code vulnerabilities, dependency issues, leaked secrets, cloud misconfigurations, and pentest findings. Developers receive pull requests with patches that match the surrounding code style, iterate on CI feedback to stay mergeable, and respond to review comments. Nullify writes fixes that patch vulnerabilities without breaking existing functionality. ## Working with Developers ### Status Updates * Posts to existing Slack threads * Updates Jira tickets with PR links * Sends notifications for reviews needed * Escalates stalled PRs to team leads ### Ownership Routing * Uses CODEOWNERS for reviewer selection * Considers team capacity (least-loaded developer) * Respects team boundaries * Coordinates multi-team changes ### Manual Fallback When automation isn't appropriate: * Provides detailed fix guidance * Creates ticket with reproduction steps * Tags appropriate owner * Preserves context for future learning --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.nullify.ai/capabilities/remediations.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.