FixVibe

// docs / ai fix prompts

AI fix prompts

Секој finding има копче Copy fix prompt под remediation. Кликнете, залепете во Claude / Cursor / Copilot, и агентот го добива канонскиот рецепт за исправка за таа vuln во framework на вашата codebase — без Claude API call од нас.

Како работи

Два дела од податоци се комбинираат при клик:

  • 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.

Како изгледа prompt

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

Прикажуваме framework-specific snippets за:

  • Next.js, React, Vue, Nuxt, Svelte (frontend)
  • Express, Fastify (Node.js backend)
  • 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.

Користете го од вашиот AI agent

Ако сте го wired up MCP server, истиот prompt е изложен како slash command. Од 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.

Зошто не го повикуваме Claude за секој click

На launch размислувавме да го повикуваме Anthropic API за секој click за да го refine prompt со codebase context. Не го направивме тоа, затоа што:

  • Agent во кој user го paste-ира prompt веќе има codebase context — користат Cursor / Claude Desktop со open repo.
  • Server-side templating covers the common remediation paths without any per-click model call.
  • Опција “Refine with AI for my codebase” може подоцна да го fire API ако users го сакаат тоа. Денес, не.
AI fix prompts — Docs · FixVibe