scope-guard

Name: scope-guard
Availability: InStock
Author: siamese001

Enforce strict code scope using AST dependency graph analysis.

Updated Oct 9, 2025

Search Tags:#git workflow #dependency analysis #code integrity #scope management #ast #auditable changes

Ready to run

npx skills add https://github.com/Siamese001/Agentic-Workflow --skill scope-guard-siamese001

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents unintended changes and scope creep by enforcing strict rules on which files can be modified during a development phase, ensuring code integrity and auditability.

Core Features & Use Cases

AST Dependency Graph Analysis: Builds and utilizes a dependency graph to justify file modifications.
Scope Pre-Check: Verifies that only declared files are modified before any edits are made.
Decontamination Protocol: Provides a clear process to revert unintended changes and restore a clean scope.
Use Case: Before refactoring a module, use this Skill to ensure you only touch the files directly related to the refactoring, preventing accidental changes in unrelated parts of the codebase.

Quick Start

Run the scope pre-check before making any code edits.

Frequently Asked Questions about scope-guard

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

FAQPage Schema

How do I prevent scope creep and unintended file modifications during code refactoring?▼

Prevent scope creep by running a scope pre-check that uses AST dependency graph analysis to verify only declared files are modified. This enforces code integrity by requiring explicit justification for all file changes before edits are made.

What is AST dependency graph analysis for code scope management?▼

AST dependency graph analysis is a technique that builds a graph of code dependencies to justify file modifications. It enforces strict code scope by verifying that changes are directly related to the declared development phase, preventing contamination.

How do I revert unintended changes and restore a clean code scope?▼

Revert unintended changes using a decontamination protocol. This protocol provides a clear process to restore a clean scope by removing accidental modifications, ensuring only authorized files remain altered in the codebase.

Can I expand the authorized code scope if a dependency requires modifying additional files?▼

Yes, you can expand the authorized code scope. The process requires explicit justification for the modification and provides revision templates to document the authorized scope expansion, maintaining auditable changes.

Does this scope management approach work without external dependencies?▼

Yes, the approach works without external dependencies. It operates as a standalone workflow component, using internal AST analysis and pre-checks to enforce code integrity and manage file modifications independently.

When should I use a scope pre-check in my git workflow?▼

Use a scope pre-check in your git workflow before making any code edits. This verifies that only declared files are modified during the development phase, preventing scope drift and ensuring auditable changes.