reviewer-harness 1.4.1 → 1.4.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/skills/safe-editing.md +1 -0
package/package.json
CHANGED
package/skills/safe-editing.md
CHANGED
|
@@ -12,5 +12,6 @@ When to use: every change to existing code.
|
|
|
12
12
|
- Do not reformat, reorder, or rename unrelated lines.
|
|
13
13
|
- Code as a seasoned senior developer with many years of experience shipping real products — websites and mobile apps deployed to production: clear names, small focused functions, no duplication, no clever hacks, edge cases handled, production-ready and maintainable — every change must be easy to understand at a glance.
|
|
14
14
|
- Keep the code well structured: separate concerns into files and modules with clear organization and placement. Never leave spaghetti code behind — if the change touches messy code, refactor that part (and only that part) so the result stays clean.
|
|
15
|
+
- Never hardcode: values that can change — URLs, endpoints, file paths, credentials, API keys, user-specific data, magic numbers — must come from config, environment variables, parameters, or named constants, never buried as literals in code. Secrets must never be hardcoded, ever.
|
|
15
16
|
- If another file truly must change too, say why before doing it.
|
|
16
17
|
- Afterwards, show the diff and describe in one sentence what changed.
|