Your code
Choose one project. Prepare its repository on GitHub or the source files in a ZIP archive.
HOW COPID_ WORKS
Share your code.
See your next step.
Start with a GitHub repository or a ZIP file.
What to prepare, how to request a check, and how to use the results.
Here is the planned diagnosis workflow.
CODE → CLARITY
01Prepare your project
02Share with GitHub or ZIP
03Explain the problem
04Use the findings to move forward
This page describes the planned workflow. This LP does not yet accept or analyze real code or connect to GitHub. You can explore sample diagnoses.
01 / BEFORE YOU START
Start with the project
you already have.
It does not need to be finished.
Gather your code, what you want to build,
and where things stop working.
Your goal and the problem
Briefly describe the feature, the behavior you expect and what actually happens.
Errors and how it runs
Gather error messages, the steps that trigger them and setup information such as a README, where available.
02 / CHOOSE YOUR WAY
Two ways to share.
Use the repository if your code is on GitHub.
Use a ZIP to share a set of files from your computer.
Choose the repository
Choose the repository and branch for the app you want checked. Make the scope clear if it contains more than one project.
Share its URL with the tool
The planned flow is to enter the repository URL in the diagnosis tool. Review the access permissions in the connection screen.
Confirm the scope and access
Confirm the branch and code in scope. Connection methods and required permissions for private repositories will be explained when the service is available.
Gather the source in one folder
Gather the source, dependency definitions, configuration files and README for the app.
Remove files that should not be shared
Leave out real secrets, .env files containing credentials and unnecessary personal data. Exclude dependency folders such as node_modules, generated builds and the .git folder from the source ZIP.
Create the ZIP and share it with the tool
The planned flow is to compress the folder as a ZIP and attach it in the tool. Supported formats, size limits and acceptance conditions will be announced when available.
03 / ADD THE CONTEXT
Give the code some context.
These four details make a useful starting point.
Share what you know.
What are you trying to do?
Example: signed-in users should see only their own data.
What actually happens?
Example: login works, but saved data does not appear.
What triggers the problem?
Example: it happens when the list page opens after login.
What have you tried?
Example: repairs you requested from AI, the changes made and error messages.
04 / READ THE FINDINGS
Use the diagnosis
to make your next move.
Use code and context to understand the issue.
Review the findings available in your plan
and decide what to work on next.
Understand the state
Light checks are planned to use deterministic tools and a lab for builds, tests, startup and configuration invariants.
Work on fixes with your AI
Review the issue and repair approach, then continue the conversation with your development AI.
Check what changed
Standard and above include production follow-up. Pro and VIP also include deeper diagnosis, prevention and handover reports.
FIRST, EXPLORE A SAMPLE.
Start with a sample diagnosis.
Before sharing real code, explore example findings and a repair prompt.