script-sprawl-guard

Name: script-sprawl-guard
Availability: InStock
Author: siamese001

Enforce canonical Python invocation patterns and prevent new runner scripts.

Updated Oct 9, 2025

Search Tags:#code quality #best practices #python #maintainability #scripting #invocation

Ready to run

npx skills add https://github.com/Siamese001/Agentic-Workflow --skill script-sprawl-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: script-sprawl-guard
Source: https://github.com/Siamese001/Agentic-Workflow/tree/main/.windsurf/skills/script-sprawl-guard
Command: npx skills add https://github.com/Siamese001/Agentic-Workflow --skill script-sprawl-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the uncontrolled proliferation of new script files for running existing Python code, ensuring a clean and maintainable codebase.

Core Features & Use Cases

Canonical Invocation Policy: Defines strict rules for how Python modules and scripts should be executed, prohibiting the creation of unnecessary wrapper scripts.
Entrypoint Decision Tree: Provides a clear, step-by-step process for determining the correct way to invoke any Python file or module.
Use Case: When a developer needs to run a Python utility, they consult the decision tree to ensure they are using the sanctioned method (e.g., python file.py or python -m module) rather than creating a new run_utility.py file.

Quick Start

Use the script-sprawl-guard skill to determine the correct invocation method for the 'data_processor.py' module.

Frequently Asked Questions about script-sprawl-guard

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

FAQPage Schema

How do I prevent Python script sprawl from too many wrapper files?▼

To prevent Python script sprawl, enforce canonical invocation patterns that prohibit creating unnecessary wrapper scripts, ensuring a clean and maintainable codebase by running modules directly via standard command line methods.

What is the best way to run a Python module without creating a new script?▼

The best way to run a Python module without a new script is to use canonical invocation methods like `python file.py` or `python -m module`, following a strict decision tree for entrypoint selection to maintain codebase maintainability.

When do I need to use python -m module instead of a wrapper executable?▼

You need to use `python -m module` instead of a wrapper executable when invoking Python utilities to comply with canonical invocation policies, which prevents the uncontrolled proliferation of new runner script files.

How do I determine the correct entrypoint for a Python utility?▼

To determine the correct entrypoint for a Python utility, consult an entrypoint decision tree that provides a step-by-step process for selecting the sanctioned canonical invocation method over creating unnecessary wrapper executables.

Why does creating new runner scripts reduce Python code maintainability?▼

Creating new runner scripts reduces Python code maintainability because it causes script sprawl, fragmenting execution patterns and cluttering the codebase with unmanaged wrapper files instead of relying on canonical invocation.

Can I use a wrapper executable for Python code if I already have one?▼

Using a wrapper executable for Python code is prohibited by canonical invocation policies, which mandate using sanctioned methods like `python file.py` to prevent script sprawl and ensure maintainable code execution.