Debugging
Paste the failing code and the full error. Ask for the root cause first, then the fix, so you learn why it broke.
Use case · software engineering

§ 01What it does well
Paste the failing code and the full error. Ask for the root cause first, then the fix, so you learn why it broke.
Give it a diff or a file and ask for bugs, edge cases and security issues, ranked by severity.
Describe the goal — smaller functions, clearer names, fewer dependencies — and ask for a step-by-step plan before code.
Ask for unit tests that cover edge cases, or for a README and docstrings that match the code you pasted.
§ 02Prompts
Open any prompt in the chat, then replace the bracketed parts with your own material.
Here is a function and the error it throws. Explain the root cause in two sentences, then give a corrected version and one test that would have caught it. Code: [paste code] Error: [paste error]
Act as a strict senior reviewer. Review this diff for bugs, edge cases, security problems and readability. List issues by severity (high, medium, low) with line references, then suggest fixes. [paste diff]
I want to refactor this module to make it easier to test. First propose a step-by-step plan with the reasons for each step. Do not write code until I approve the plan. [paste module]
§ 03Tips
§ 04FAQ
In our chat, GLM-5.3. Z.ai built it for complex software engineering and reports large coding gains over GLM-5.2. GLM-5.3 Flash is a fast, free-flowing alternative for smaller tasks.
GLM-5.3 supports about one million tokens of context through the API. Our free chat trims very long conversations to keep requests fast, so paste the files that matter most.
Yes, with GLM-5.3 Flash. Attach the screenshot and ask what went wrong.
§ 05More
Try it now
No account, no card, no install. Type a question and watch GLM-5.3 Flash answer in seconds — switch to GLM-5.3 for the hardest problems.