skills.rest
Gold-b
Gold-bCOMMUNITY
Explore all skills by this author →
GitHub

impact-safe-executor

Enforce edit scope and validation evidence before code modifications.

8|Updated Apr 12, 2026
Search Tags:#pre-write#validation#impact analysis#governance#regression prevention#code safety#scope enforcement
One-click install
npx skills add https://github.com/Gold-b/claude-code-governance --skill impact-safe-executor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: impact-safe-executor
Source: https://github.com/Gold-b/claude-code-governance/tree/main/bundle/skills/impact-safe-executor
Command: npx skills add https://github.com/Gold-b/claude-code-governance --skill impact-safe-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent unintended regressions during code changes by forcing a clear edit scope, mapping downstream impact, and requiring real validation evidence before work is marked complete.

Core Features & Use Cases

  • Pre-write impact analysis: Reviews in-scope files, dependencies, contracts, conventions, schemas, and known gotchas before any code modification.
  • Scope enforcement: Stops work when a change would touch unapproved files or when a high-risk file is about to be edited without explicit approval.
  • Evidence-based completion: Requires concrete validation output such as tests, lint, builds, probes, or logs before updating project state.
  • Use case: When fixing a bug in a shared service or config file, use this Skill to identify callers, affected APIs, regression zones, and approval checkpoints before making the smallest safe edit.

Quick Start

Ask the AI to use impact-safe-executor with your goal, approved plan section, allowed file scope, stop condition, and validation requirements before making any code change.

Frequently Asked Questions about impact-safe-executor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent unintended regressions when modifying shared modules or configuration files?▼

To prevent unintended regressions during code modifications, you can enforce a strict edit scope, map downstream impact, and require validation evidence like test or build output before marking work complete.

What is pre-write impact analysis and how does it protect routing logic from unsafe edits?▼

Pre-write impact analysis reviews in-scope files, dependencies, schemas, and known gotchas before any code modification, protecting routing logic by identifying affected APIs and regression zones before changes are applied.

How do I enforce scope restrictions and require approval gates for high-risk file edits?▼

You can enforce edit scope by defining allowed file boundaries and stop conditions, which halts work automatically if an unapproved or high-risk file is targeted without explicit approval.

Can I use manifest-based path resolution to ensure concurrency safety during governed software edits?▼

Yes, manifest-based path resolution supports governed software edits by mapping exact file targets, ensuring concurrency safety, and enforcing minimal one-step edits for shared service modifications.

What is the best way to require concrete validation evidence before completing code changes?▼

The best way to require validation evidence is to mandate concrete output such as tests, lint results, builds, probes, or logs before any project state is updated and the edit is marked complete.

Why does fixing a bug in a shared service require downstream impact mapping before editing?▼

Downstream impact mapping is required before editing a shared service to identify callers, affected APIs, and regression zones, ensuring the smallest safe edit is made within an approved scope.

Related Skills

Explore More Software Engineering Skills→
Vel-LabsVel-Labs

feature-implementation-runner

Transform approved phase plans into scoped code or documentation changes.

Official
Intermediate
allexcdallexcd

verification

Require tests, logs, diffs, or behavioral checks before marking tasks complete.

Community
Intermediate
ElliotJLTElliotJLT
60

trace-it

Traces callers and dependents before editing shared code to map impact.

Community
Basic
AminAlamAminAlam
26

Automated Testing in CI/CD

Automate test execution and gating in CI/CD pipelines for medical devices.

Community
Intermediate