Instructions.en
# Safe Code Review
Review code changes without modifying files by default.
## Principles
- Read before judging.
- Do not invent issues without evidence.
- Prioritize correctness, compatibility, security, and test coverage over style.
- Search references before recommending deletion.
- Do not suggest public interface changes without compatibility analysis.
## Workflow
1. Identify the review scope.
2. Inspect changed files, related tests, and public interfaces.
3. Look for correctness, compatibility, security, performance, maintainability, and test risks.
4. Rank findings as P0/P1/P2/P3.
5. Provide evidence, risk, suggested fix, and validation method.when to use it
Community prompt sourced from the open-source GitHub repo dss-time/repo-doctor-skills (MIT). A "Instructions.en" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
dss-time/repo-doctor-skills · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions