surgical-changes

Establish change boundaries to ensure minimal, task-specific code modifications.

65|10|Updated May 1, 2026
One-click install
npx skills add https://github.com/DevelopersGlobal/ai-agent-skills --skill surgical-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: surgical-changes
Source: https://github.com/DevelopersGlobal/ai-agent-skills/tree/main/skills/surgical-changes
Command: npx skills add https://github.com/DevelopersGlobal/ai-agent-skills --skill surgical-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain high code quality by ensuring only necessary changes are made during code modifications, preventing unnecessary refactoring and stylistic changes.

Core Features & Use Cases

  • Prevent Unnecessary Refactoring: Avoids drive-by refactoring and stylistic changes that don't directly relate to the task.
  • Boundary Establishment: Allows setting explicit boundaries for changes, reducing scope creep.
  • Task-Specific Modifications: Ensures every change is directly traceable to the task, enhancing trust in code reviews.
  • Use Case: When making code changes, this Skill ensures that only the intended code is modified, preserving the integrity of the rest of the codebase.

Quick Start

Before modifying any code, activate the surgical-changes skill and strictly follow the guidelines for establishing change boundaries and reviewing your changes.

Frequently Asked Questions about surgical-changes

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

FAQPage Schema
How do I prevent unnecessary code changes during refactoring?

Unnecessary code changes are prevented by establishing explicit change boundaries before modification and tracing every edit directly to the task request, eliminating drive-by refactoring and stylistic adjustments.

What is drive-by refactoring and how does it affect code quality?

Drive-by refactoring involves making stylistic changes or code modifications unrelated to the current task, which degrades code quality by expanding the scope and making code reviews harder to trust.

How do I set boundaries for code modifications before a programming task?

Setting boundaries for code modifications requires careful planning to define exactly what code will be changed, ensuring only necessary and task-specific modifications are made while preserving the rest of the codebase.

Can I restrict code modifications to only what is requested in the task?

You can restrict code modifications by ensuring every change is directly traceable to the user's request, which maintains codebase integrity and enhances trust during code reviews.

What is the best way to ensure minimal code changes in a pull request?

The best way to ensure minimal code changes is to establish explicit boundaries beforehand and verify that each modification is necessary and directly traceable to the original task request.