name	safe-edit-simulator
description	Produce a dry-run diff plus a risk checklist and rollback plan for any potentially disruptive change.
license	MIT
metadata	{"mode":"planning","purpose":"safety"}

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

Dry-run diff: summary of files and hunks.
Risk checklist: 3-8 items with severity.
Rollback: single-line plan.
Verify: 1-3 commands.

Related Skills

fix-suggester, patch-applier, qa-orchestrator

Más de este repositorio

mismo repositorio

ci-orchestrator

pilinux/gorest

Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.

2026-06-24502

linter-runner

pilinux/gorest

Execute repository linters and surface highest-priority issues with minimal, targeted fixes.

2026-06-24502

ast-introspection

pilinux/gorest

Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).

2026-02-19502

build-run

pilinux/gorest

Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.

2026-02-19502

code-formatter

pilinux/gorest

Apply repository-standard formatting to minimize diff noise and meet linter expectations.

2026-02-19502

code-navigation

pilinux/gorest

Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.

2026-02-19502

name	safe-edit-simulator
description	Produce a dry-run diff plus a risk checklist and rollback plan for any potentially disruptive change.
license	MIT
metadata	{"mode":"planning","purpose":"safety"}

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

Dry-run diff: summary of files and hunks.
Risk checklist: 3-8 items with severity.
Rollback: single-line plan.
Verify: 1-3 commands.

Related Skills

fix-suggester, patch-applier, qa-orchestrator