edit

Apply scoped file edits with citations and contract guardrails.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/espensev/ai-skills --skill edit-espensev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edit
Source: https://github.com/espensev/ai-skills/tree/main/gemini-skills/skills/edit
Command: npx skills add https://github.com/espensev/ai-skills --skill edit-espensev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables precise, contract-bound edits to code and documentation, ensuring changes stay within defined scope and follow governance rules.

Core Features & Use Cases

  • Scoped edits: Apply surgical changes strictly within the designated files and lines, respecting the Planning Contract.
  • Evidence-driven edits: Require citations of file paths and line numbers before making modifications to preserve traceability.
  • Guardrail compliance: Enforce contract-based constraints and global guardrails during every edit operation.

Quick Start

Apply a scoped edit to the target file within the contract boundary to implement the requested change.

Frequently Asked Questions about edit

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

FAQPage Schema
How do I apply scoped code edits without breaking other parts of the file?

Scoped code edits require applying surgical changes strictly within designated files and lines. By enforcing a Planning Contract, changes are constrained to the designated scope, ensuring modifications do not break unrelated parts of the file.

What is evidence-driven editing for source files?

Evidence-driven editing requires concrete citations of file paths and line numbers before making modifications. This approach preserves traceability and ensures every code change is backed by specific file evidence.

How do I enforce guardrails when updating project configurations?

To enforce guardrails when updating project configurations, apply contract-based constraints during every edit operation. This ensures configuration updates follow governance rules and stay within defined boundaries.

Can I use contract-bound edits for documentation tweaks?

Yes, contract-bound edits apply to both code and documentation. The skill handles surgical changes to documentation tweaks while respecting the Planning Contract and enforcing global guardrails.

What is the best way to ensure traceability during code fixes?

The best way to ensure traceability during code fixes is requiring concrete file and line citations before changes. This evidence-based approach enforces the 13-element Planning Contract, constraining writes to the designated scope.

Why does scoped editing require a Planning Contract?

Scoped editing requires a Planning Contract to constrain writes to the designated scope and enforce governance rules. The 13-element contract ensures modifications are surgical, evidence-based, and comply with global guardrails.