Prompts are available in English and Simplified Chinese. Showing English.
Run one project health check
Find an existing check and return evidence or a repair draft.References & what we used
- Best practices: Give Claude a way to verify its work
Uses build results as verification; command selection, preflight checks, timeout and repair boundaries are whenreset additions.
Inspect project scripts and choose one lightweight local typecheck or build. Read its definition and referenced scripts first. Run only if it needs no installation, credentials or network access and does not publish, migrate data or edit source. Otherwise report a static inspection. Run it once with a timeout of at most sixty seconds. Report missing dependencies or timeouts without changing the environment. On success, state the command and result. On failure, investigate only the first actionable cause, distinguishing environment problems from code defects. For a confirmed defect, deliver its location, evidence, a complete minimal repair draft and verification command. Do not suppress checks. Mark proposed repairs unapplied and unverified; when the cause remains uncertain, report the remaining evidence instead of inventing a patch. Execution contract: Start directly. Do not ask me to approve a plan, choose files or fill in a template. Use only this project, this conversation and materials already provided; do not search unrelated projects or private history. Complete what the evidence supports and report missing inputs. If the task is inapplicable, explain why and stop without inventing a result. Preserve existing files and uncommitted changes. Include complete proposed content in your reply; standalone artifacts may be saved under a new, unused filename. Do not install dependencies, change the environment, commit, push or deploy. Respect access and permission limits and report blocked work. Check your result once, deliver it and stop without asking whether to continue.