refactor-squatters

Detect namespace integrity violations in large Python projects and produce structured audits.

6|1|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/JordanGunn/skills --skill refactor-squatters
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactor-squatters
Source: https://github.com/JordanGunn/skills/tree/main/skills/refactor/squatters
Command: npx skills add https://github.com/JordanGunn/skills --skill refactor-squatters

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Detects modules or packages that occupy a namespace position they do not semantically own, helping teams maintain domain coherence and avoid navigational ambiguity in large codebases.

Core Features & Use Cases

  • Identifies five namespace integrity violation patterns: utility dumps, stuttery siblings, thin wrappers, axis violations, and semantic diffusion.
  • Scans project structure to surface misplaced concepts and provides prioritized remediation directions (move, rename, or consolidate).
  • Generates a readable audit report and references for human review.

Quick Start

Run a structural audit to identify namespace squatters and report actionable remediation suggestions.

Frequently Asked Questions about refactor-squatters

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

FAQPage Schema
How do I detect namespace integrity violations in a large Python project?

Detect namespace integrity violations by scanning project structure to surface misplaced concepts like utility dumps and semantic diffusion, producing a structured audit report with severity classifications and remediation hypotheses for human review.

What are namespace squatters and structural smells in code architecture?

Namespace squatters are modules occupying a namespace position they do not semantically own, creating navigational ambiguity and domain coherence issues. This structural smell includes patterns like stuttery siblings, thin wrappers, and axis violations.

Can I audit a large Python codebase for semantic diffusion and thin wrappers?

Yes, you can audit large Python codebases to identify five namespace integrity violation patterns including semantic diffusion and thin wrappers, generating an actionable report with prioritized remediation directions like move, rename, or consolidate.

What is the best way to fix stuttery siblings and utility dumps in Python packages?

The best way to fix stuttery siblings and utility dumps is running a structural audit that surfaces these namespace violations, then applying prioritized remediation directions to move, rename, or consolidate the misplaced modules into coherent domain boundaries.

Does this namespace audit work for small Python projects or only large codebases?

This namespace audit applies specifically to large Python projects. It scans project structure to surface misplaced concepts and domain coherence issues, making it most effective for codebases where navigational ambiguity and structural smells have accumulated.