FixVibe

// docs / ai fix prompts

Prompts de correção com IA

Cada finding tem um botão Copiar prompt de correção abaixo da remediação. Clique, cole no Claude / Cursor / Copilot, e o agente recebe a receita canônica de correção dessa vuln no framework do seu código — sem chamada nossa à API do Claude.

Como funciona

Duas peças de dados se combinam no clique:

  • The finding — the issue summary, affected surface, remediation guidance, and safe evidence needed to help your coding agent fix it.
  • Your app context — FixVibe uses scan context when available to choose a framework-aware remediation shape, and falls back to a generic recipe when it cannot infer enough context.

Fix prompts are rendered server-side from FixVibe remediation guidance. They are designed for copy-paste use in Cursor, Claude Desktop, Copilot, or another coding agent without exposing the internal prompt registry in the browser.

Como o prompt se parece

Fix the "Reflected XSS in /search?q=" vulnerability at /search.

Issue: Query parameter q is rendered into the response body without
escaping; an attacker can inject <script> via crafted URLs.

Codebase context: Next.js.

Recommended fix:
In Next.js, render user-supplied values through JSX ({value}) so React's
automatic escaping kicks in. For server components rendering rich HTML,
sanitize with DOMPurify (server-side via JSDOM) before output.

Constraints:
- Don't break existing tests; run the test suite after the change.
- Match the codebase's existing style and lint config.
- Add a brief comment explaining the security reasoning only where the
  fix would otherwise look arbitrary.
- If the fix needs a new dependency, install it via the project's
  package manager (npm / pnpm / pip / bundle / composer).

Reference: CWE-79 — see https://cwe.mitre.org/data/definitions/79.html

Frameworks compatíveis

Mostramos snippets específicos por framework para:

  • Next.js, React, Vue, Nuxt, Svelte (frontend)
  • Express, Fastify (backend Node.js)
  • Django, Flask (Python)
  • Ruby on Rails
  • Laravel (PHP)
  • ASP.NET Core fallback guidance

Framework context is best-effort. If FixVibe cannot infer enough safely from the scan, the prompt asks your coding agent to inspect the repository before applying the fix.

Use a partir do seu agente de IA

Se você conectou o servidor MCP, o mesmo prompt é exposto como comando slash. No Claude Desktop:

/fixvibe-fix finding_id=550e8400-e29b-41d4-a716-446655440000

The server looks up the finding, applies available scan context, renders the remediation prompt, and injects it into your conversation as the user message. No third-party LLM API call is made by FixVibe for this templated prompt.

Por que não chamamos o Claude a cada clique

No lançamento, consideramos chamar a API Anthropic a cada clique para refinar o prompt com contexto do código. Não fizemos isso porque:

  • O agente em que o utilizador cola já tem contexto do código — ele está usando Cursor / Claude Desktop com o repo aberto.
  • Server-side templating covers the common remediation paths without any per-click model call.
  • Uma opção “Refinar com IA para o meu código” poderia chamar a API mais tarde se os utilizadores quiserem. Hoje, não.
Prompts de correção com IA — Docs · FixVibe