safe-edit-simulator
Installation
SKILL.md
Safe Edit Simulator
When to Use
- Before applying changes that affect auth, security, DB migrations, middleware, or deployment behavior.
Responsibilities
- Produce a readable dry-run diff and summarize changed hunks.
- Enumerate risks and mitigation steps.
- Provide a concise rollback plan and verification commands.
Rules
- Do not apply changes; only simulate and document.
- Call out impacts on authentication, token validation, env/config, and data integrity.
Output
Related skills
More from pilinux/gorest
file-reader
Precisely read source files or snippets and return concise, citation-backed facts needed for decisions or edits.
28code-navigation
Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.
7fix-suggester
Diagnose failures and propose minimal, test-backed fixes with verification and rollback instructions.
7build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
7logs-repro-harness
Reduce flaky or environment-dependent failures to a minimal, reproducible script and capture the exact logs and error lines.
7ci-orchestrator
Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.
6