AI Coding Assistant
Debug code, write scripts, refactor projects, explain errors, and ask for tests instead of guesses.
Start this task in Mother →No account required. The example opens in your composer; edit it before sending. Use uncensored AI for useful work with fewer content restrictions, not a guarantee of an answer.
What to provide
Name the language, runtime version and the smallest function or file involved. Include its intended contract, example input, expected output and dependencies already installed. Ask for a patch that matches the existing project rather than a replacement application. Remove API keys, tokens and customer data before pasting code. For a new script, specify how you will run it and what must happen when input is missing or malformed. Request tests before relying on the result; a plausible code block is not evidence that it ran.
Example starting request
Help me with coding. Debug code, write scripts, refactor projects, explain errors, and ask for tests instead of guesses. Explain your reasoning and identify anything I should verify.
Worked example
Illustrative example, not a generated result or a user transcript.
Coding brief: “My JavaScript helper must keep the first occurrence of each label in order. Input: ["green", "black", "green"]. Expected: ["green", "black"]. Labels are strings and comparisons are case-sensitive. Explain a minimal implementation and give tests for an empty list, repeated labels and labels that differ only in case.” An illustrative approach is to iterate in order, track previously seen labels and append only the first occurrence.
This brief defines both duplicate handling and ordering, so a suggestion that sorts the list would be wrong even if it removed duplicates. A Set-based approach can fit the stated string contract, but that does not establish the correct behavior for objects, normalized text or a different runtime. Have Mother state assumptions and explain each changed line. This example is a reasoning scaffold, not an executed benchmark or a claim that the code has been tested inside your repository.
Check the answer
Run the proposed tests in your own environment, then run adjacent project tests and inspect the diff. Confirm the answer uses installed libraries and real APIs rather than invented imports. Check boundary inputs and failure handling, not just the example. For file writes, databases or deployment scripts, use a disposable fixture before production. Mother does not gain access to your private repository merely because you name it. Supply the relevant context yourself, and reject claims of executed tests unless actual execution evidence is available.