organize_project

Audit repository directory structures and clean up misplaced files.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/tatsuki-washimi/gwexpy --skill organize-project-tatsuki-washimi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: organize_project
Source: https://github.com/tatsuki-washimi/gwexpy/tree/main/.agent/skills/organize_project
Command: npx skills add https://github.com/tatsuki-washimi/gwexpy --skill organize-project-tatsuki-washimi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Project directories often become tangled, making it hard to maintain clean builds, predictable imports, and correct ignore rules. This skill audits a repository's structure, identifies misplaced files, consolidates organization patterns, and suggests or applies gitignore improvements to keep the workspace tidy.

Core Features & Use Cases

  • Audit root and common package directories to flag misplaced files and empty directories.
  • Propose and apply sensible folder structures, and ensure test and source directories follow conventions.
  • Update .gitignore entries to prevent tracking of build artifacts and sensitive data in team repositories.

Quick Start

Run the organize_project skill on your repository to audit structure and clean up ignore rules.

Frequently Asked Questions about organize_project

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

FAQPage Schema
How do I audit my project directory structure for misplaced files?

You can clean up misplaced files by running this skill to audit your repository's root and common package directories. It identifies misplaced files and empty directories, then proposes and applies sensible folder structures to keep your workspace tidy.

What is the best way to update .gitignore entries for build artifacts and sensitive data?

Updating .gitignore entries to prevent tracking build artifacts and sensitive data is handled by auditing ignore rules. This skill suggests and applies gitignore improvements to ensure team repositories exclude unnecessary or sensitive files from version control.

Can I use this project organization tool for software repositories of any size?

Yes, this project organization tool applies to software repositories of any size. It operates locally without external services, making it suitable for maintaining clean builds and predictable imports across small projects or large team repositories during releases and onboarding.

How do I consolidate directory organization patterns during a project handoff?

Consolidating directory organization patterns during a project handoff requires auditing the codebase structure and cleaning up misplaced files. This skill automates that housekeeping, ensuring safety and reproducibility by enforcing simple validation around file moves and gitignore adjustments.

Does cleaning up a codebase directory structure require external services or network access?

Cleaning up a codebase directory structure does not require external services or network access. This skill operates entirely locally, enforcing simple validation around file moves and gitignore adjustments to ensure safety and reproducibility during the organization process.

Why does my project directory structure become tangled and hard to maintain?

Project directory structures become tangled when misplaced files accumulate and ignore rules are not updated, making clean builds and predictable imports difficult. This skill audits the repository to identify misplaced files and consolidate organization patterns to keep the workspace tidy.