// docs / ai fix prompts
AI fix prompts
Ny finding tsirairay dia manana bokotra Copy fix prompt eo ambanin’ny remediation. Kitiho, apetaho ao amin’i Claude / Cursor / Copilot, ary mahazo ny fomba fanamboarana ofisialy ho an’ilay vuln ao amin’ny framework an’ny codebase-nao ilay agent; tsy misy antso Claude API avy aminay.
Fomba fiasany
Data roa no mitambatra rehefa tsindriana:
- 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.
Endriky ny 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.htmlFrameworks tohanana
Mampiseho snippets manokana isaky ny framework izahay ho an’ny:
- 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.
Ampiasao avy amin’ny AI agent-nao
Raha efa nampifandray ny MCP server ianao, aseho ho slash command ilay prompt mitovy. Avy amin’i 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.
Antony tsy iantsoanay Claude isaky ny clic
Tamin’ny fanombohana dia nodinihinay ny hiantso Anthropic API isaky ny clic mba hanatsara ny prompt amin’ny context an’ny codebase. Tsy nataonay izany satria:
- Ilay agent ametahan’ny mpampiasa ny prompt dia efa manana context an’ny codebase: mampiasa Cursor / Claude Desktop izy miaraka amin’ny repo misokatra.
- Server-side templating covers the common remediation paths without any per-click model call.
- Safidy opt-in “Refine with AI for my codebase” dia afaka mampandeha ny API any aoriana raha ilain’ny mpampiasa. Androany, tsia.
