> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/fix/guardrail-auto-fix.md).

# Guardrail Auto-Fix

Fix an eligible vulnerability on the pull request itself. The full walkthrough lives with PR Guardrails.

When a guardrail flags a new, eligible dependency vulnerability or SAST finding on a pull request, you don't have to leave the PR to fix it. Heeler offers a **Fix w/Heeler** action (a one-click **Apply suggestion** on GitHub, or a direct commit to the branch on GitLab/Bitbucket) that upgrades the dependency or applies a targeted code fix on the PR's own branch, validates the change by building it, and pushes it back — then the guardrail re-runs automatically.

It's the same remediation as the finding-side fixes — [SCA Auto-Fix](/mrecEO40m5D6bt7Pq5pE/fix/sca-auto-fix.md) for dependencies, [SAST Auto-Fix](/mrecEO40m5D6bt7Pq5pE/fix/sast-auto-fix.md) for code — just triggered from the pull request instead of from findings. It appears here in Fix because it's the PR-side counterpart to the finding-side fixes — same remediation, entered from an open pull request rather than from your findings list.

{% hint style="info" %}
The full step-by-step — the GitHub/GitLab triggers, what's eligible, and how checks re-run — lives on the canonical page: [**PR Guardrails → Guardrail Auto-Fix**](/mrecEO40m5D6bt7Pq5pE/prevent/pr-guardrails/guardrail-auto-fix.md).
{% endhint %}

## Related

* [PR Guardrails → Guardrail Auto-Fix](/mrecEO40m5D6bt7Pq5pE/prevent/pr-guardrails/guardrail-auto-fix.md) — the complete walkthrough.
* [SCA Auto-Fix](/mrecEO40m5D6bt7Pq5pE/fix/sca-auto-fix.md) · [SAST Auto-Fix](/mrecEO40m5D6bt7Pq5pE/fix/sast-auto-fix.md) · [Automate Remediation](/mrecEO40m5D6bt7Pq5pE/fix/automate-remediation.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/fix/guardrail-auto-fix.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.