AI ਫਿਕ੍ਸ ਪ੍ਰॉਮ੍ਪ੍ਟ

ਇਹ ਕੈਸੇ ਕਾਮ ਕਰਤਾ ਹੈ

Click ਪਰ data ਕੇ ਦੋ ਹਿਸ੍ਸੇ combine ਹੋਤੇ ਹਨ:

• 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

Supported 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 ਸੇ ਇਸ੍ਤੇਮਾਲ ਕਰੋ

ਅਗਰ ਤੁਸੀਂਨੇ MCP server wire ਕਿਯਾ ਹੈ, ਤੋ ਉਹੀ prompt slash command ਕੇ ਰੂਪ ਮੇਂ exposed ਹੈ। 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.

ਅਸੀਂ ਹਰ click ਪਰ Claude ਕ੍ਯੋਂ ਨਹੀਂ hit ਕਰਤੇ

Launch ਪਰ ਅਸੀਂਨੇ ਸੋਚਾ ਥਾ ਕਿ ਹਰ click ਕੇ ਲਿਏ Anthropic API call ਕਰਕੇ codebase context ਸੇ prompt refine ਕਰੋ। ਅਸੀਂਨੇ ਐਸਾ ਨਹੀਂ ਕਿਯਾ, ਕ੍ਯੋਂਕਿ:

• ਜਿਸ agent ਮੇਂ user paste ਕਰਤਾ ਹੈ ਉਸਕੇ ਪਾਸ ਪਹਲੇ ਸੇ codebase context ਹੋਤਾ ਹੈ — ਵੇ Cursor / Claude Desktop ਮੇਂ repo open ਰਖਕਰ ਕਾਮ ਕਰ ਰਹੇ ਹੋਤੇ ਹਨ।
• Server-side templating covers the common remediation paths without any per-click model call.
• “ਮੇਰੇ codebase ਕੇ ਲਿਏ AI ਸੇ refine ਕਰੋ” opt-in ਬਾਦ ਮੇਂ API fire ਕਰ ਸਕਤਾ ਹੈ ਅਗਰ users ਚਾਹੇਂ। ਆਜ, ਨਹੀਂ।