Skip to content
MMake Prompt AI Get Started
Home > ChatGPT Guide > /bugfix
Custom prompt shortcut / Software Development

/bugfix — ChatGPT Prompt Guide

Explore the /bugfix custom ChatGPT prompt shortcut with a practical template, examples, and review steps. Learn how to refine outputs for your workflow.

What does /bugfix do?

Purpose: Investigate a JavaScript form that submits twice after reopening a modal.

This is a custom prompt convention, not a built-in or official ChatGPT slash command. Entering the slash text alone does not guarantee that ChatGPT will invoke a special tool. Use the complete structured prompt below or configure your own app to interpret this shortcut.

Key decision for this workflow

Count submit listeners across modal open/close cycles; compare click versus submit events; attach handlers once or clean them up.

Copy-ready task brief

/bugfix Objective: Investigate a JavaScript form that submits twice after reopening a modal. Inputs: Minimal reproduction, event-handler code, browser console output, and submission network trace. Deliverable: A root-cause explanation, smallest safe patch, and regression test.

Reusable prompt template

/bugfix Objective: Investigate a JavaScript form that submits twice after reopening a modal. Available materials: Minimal reproduction, event-handler code, browser console output, and submission network trace. Required output: A root-cause explanation, smallest safe patch, and regression test. Acceptance test: Count submit listeners across modal open/close cycles; compare click versus submit events; attach handlers once or clean them up. Boundary: Disabling the submit button may hide duplicate requests but does not repair duplicated event registration. Return the requested deliverable first, then a brief verification checklist and any unresolved questions.

How to use this shortcut

  1. Collect the source inputs: Minimal reproduction, event-handler code, browser console output, and submission network trace.
  2. Run /bugfix with the copy-ready task brief above.
  3. Request the concrete output: A root-cause explanation, smallest safe patch, and regression test.
  4. Check the result: Count submit listeners across modal open/close cycles; compare click versus submit events; attach handlers once or clean them up.

Quality checks and limitations

Acceptance criteria: Count submit listeners across modal open/close cycles; compare click versus submit events; attach handlers once or clean them up. Limitation: Disabling the submit button may hide duplicate requests but does not repair duplicated event registration.

Related tools and learning

Continue with the 35 prompt generators, the technical AI Guides, and the Image Guides for deeper examples.

/code/debug/refactor/codeaudit/marketresearch/heroimage

Worked example and expected output

Input materials: Minimal reproduction, event-handler code, browser console output, and submission network trace.

Requested result: A root-cause explanation, smallest safe patch, and regression test.

Acceptance test: Count submit listeners across modal open/close cycles; compare click versus submit events; attach handlers once or clean them up.

Field workflow: inputs, decisions, and validation

When to use this shortcut: Investigate a JavaScript form that submits twice after reopening a modal.

What to provide: Minimal reproduction, event-handler code, browser console output, and submission network trace.

What to request: A root-cause explanation, smallest safe patch, and regression test.

Practical method: Count submit listeners across modal open/close cycles; compare click versus submit events; attach handlers once or clean them up.

Important limitation: Disabling the submit button may hide duplicate requests but does not repair duplicated event registration.

Frequently asked questions

Is /bugfix an official ChatGPT command? No. It is a reusable custom shorthand from this catalog. Does it work without a plugin? You can copy the full prompt into an assistant; automatic slash-command routing requires application logic. Can the output be trusted without review? No. Review accuracy, safety, and suitability before use.

Worked scenario and review

Scenario: Diagnose a JavaScript form that submits twice after a modal reopens.

Expected deliverable: Describe reproduction steps, suspected duplicate listeners, a patch and a regression test.

Verification: Confirm the handler runs exactly once.