organized-codebase-applicator

Apply the Organized Codebase template to standardize project structure and archive redundant folders.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/jhillbht/hackathon-clipper-program --skill organized-codebase-applicator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: organized-codebase-applicator
Source: https://github.com/jhillbht/hackathon-clipper-program/tree/main/Library/Mobile Documents/com~apple~CloudDocs/BHT Promo iCloud/Organized AI/Windsurf/google-marketing-hub-mcp/.claude/skills/organized-codebase-applicator
Command: npx skills add https://github.com/jhillbht/hackathon-clipper-program --skill organized-codebase-applicator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Applies the Organized Codebase template to existing projects and performs intelligent cleanup of unused or redundant directories.

Core Features & Use Cases

  • Analyze project structure and size
  • Archive iteration/legacy directories (e.g., -v*, -old, -backup) into .archive
  • Copy Organized Codebase template directories (PLANNING, ARCHITECTURE, etc.)
  • Merge .gitignore files and update project placeholders
  • Automate final git operations for clean handoff

Quick Start

bash scripts/apply-organized-codebase.sh --target /path/to/project

Frequently Asked Questions about organized-codebase-applicator

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

FAQPage Schema
How do I organize and standardize an existing codebase structure?

Organize a codebase by applying the Organized Codebase template, which standardizes directories like PLANNING, ARCHITECTURE, DOCUMENTATION, and SPECIFICATIONS. The Skill analyzes your project structure, archives redundant folders, and applies template directories to enforce consistent layout across components.

Can I safely remove old iteration folders and cleanup without losing work?

Yes. The Skill archives legacy directories (e.g., -v*, -old, -backup) into .archive rather than deleting them, preserving all artifacts. It also identifies regenerable directories like node_modules and dist that can be safely removed during cleanup.

What happens during codebase template application—does it overwrite my files?

Template application merges new structure with existing files. It copies template directories, updates .gitignore by merging entries, and replaces project placeholders. Dry-run and force modes let you preview changes or control the workflow before committing.

How do I automate cleanup and handoff workflows for messy projects?

Run the apply-organized-codebase script with target path and optional flags for dry-run, force, or git-commit modes. The Skill handles archive creation, template copying, .gitignore merging, and final git operations in one workflow to standardize project layout.

Does this work with any project type or are there prerequisites?

The Skill works on any project with a filesystem structure. Prerequisites include a target project directory and optionally git initialization for commit workflows. No external dependencies are required; it operates on directory trees and configuration files already in place.

What's the best way to handle redundant directories before scaling a project?

Archive iteration variants into .archive and apply the Organized Codebase template to standardize structure before handoff or scaling. This removes clutter, enforces consistent naming, and preserves legacy versions for reference without cluttering the active codebase.