Map an unfamiliar repository
Map entry points, dependencies, and the relevant tests. Cite files for each finding.
Adapt a prompt to your repository. Keep the boundaries. Verify the assumptions.
Map entry points, dependencies, and the relevant tests. Cite files for each finding.
Compare README, package manifest, and lockfile. Do not invent a command.
Trace the caller, implementation, and tests for the target behavior.
Inspect existing files before choosing architecture. Compare three substantial options.
Define observable acceptance criteria and explicitly excluded behavior.
Compare a focused change, an extraction, and a broader redesign. Explain the smallest sufficient choice.
Record input, expected behavior, actual behavior, and a minimal reproduction.
List competing causes and design an experiment that distinguishes them.
Make the regression fail before the fix and pass afterward. Preserve existing assertions.
Inspect assertion changes and whether the tests still establish the intended behavior.
Identify intentional behavior and boundary cases before changing structure.
Preserve named invariants, callers, and error behavior while changing structure.
Identify actionable correctness findings and unrelated changes. Explain each with evidence.
Identify the base revision and review the full diff, including tests and configuration.
Document commands only after verifying them against repository facts.
Record mutable state, evidence, unresolved issues, and a concrete next action.
Use semantic controls, visible focus, and accessible error states. Verify with keyboard use.
Check narrow widths, text enlargement, and long-content behavior.
Inspect existing authorization and validation patterns. Define success and failure behavior.
Check missing inputs, unauthorized access, and dependency failures.
Inspect schema and data assumptions. Define rollback and test on a disposable database.
Measure a representative case, isolate the bottleneck, and compare after the change.
Trace untrusted input, authorization, and external data flow. Do not export secrets.
Summarize the concrete problem, changed behavior, verification, and limitations.
Preserve both requirements, inspect each diff, and verify the integrated result.
Confirm the intended revision, fetch referenced assets, and exercise the changed behavior.
Identify the environment and applicable official configuration documentation before suggesting fields.
Include concise commands, boundaries, and conventions supported by repository evidence.
Partition independent work, define ownership, and plan synthesis and integration checks.
Resolve variables, verify preconditions, and keep environment-specific syntax explicit.