script-modify

Update, refactor, or delete Python automation scripts with explicit path input.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill script-modify-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: script-modify
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/script-modify
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill script-modify-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers safely update, refactor, or delete Python automation scripts by enforcing a standard workflow and SSOT practices to prevent drift.

Core Features & Use Cases

  • Update: modify an existing automation script to fix bugs or adjust behavior.
  • Refactor: restructure code to improve readability, maintainability, and testability without altering external behavior.
  • Delete: safely remove obsolete scripts with clear deprecation checks and cleanup steps.

Quick Start

Run /script-modify <path> [--action <type>] to apply the requested change.

Frequently Asked Questions about script-modify

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

FAQPage Schema
How do I safely update a Python automation script without causing workflow drift?

To safely update a Python automation script, you need a standardized workflow that enforces SSOT practices and explicit path input to prevent drift. This approach guides modifications by requiring a specified file path and a defined action type to constrain changes.

What is the best way to refactor Python code in an automation project without altering external behavior?

Refactoring Python code in an automation project involves restructuring the script to improve readability, maintainability, and testability while preserving its external behavior. This is achieved by applying a controlled modification type specifically designated for refactoring tasks.

How do I securely delete obsolete Python scripts from my automation workflow?

To securely delete obsolete Python scripts from an automation workflow, you should use a controlled process that includes clear deprecation checks and explicit prompts for destructive actions. This ensures safe removal and cleanup steps are followed before final deletion.

Does this Python script modification approach require specific command arguments?

Yes, this Python script modification approach requires an explicit path input to target the specific file. It also uses an optional action type argument—such as update, refactor, or delete—to guide and constrain the specific change applied to the automation script.

Why should I use explicit prompts when deleting automation scripts?

You should use explicit prompts when deleting automation scripts because destructive actions can permanently remove critical workflow components. Explicit prompts enforce a safe, auditable change process by requiring confirmation before executing any irreversible deletions.