Project layout refactor
Skill yigityildiz0/universal-ai-skill-library/skills/common/project-layout-refactor
531 searchable AI Agent Skills for Claude Code, OpenAI Codex, and OpenCode — EN/TR catalog, platform and risk notes, direct ZIPs, and curated bundles.
npx -y skills add yigityildiz0/universal-ai-skill-library --skill project-layout-refactorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Audit and safely refactor a repository's directory layout while preserving behavior, imports, build tooling, history, generated-file rules, and user.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.4 KB, as published. Nobody here has run it
Project Layout Refactor
Analyze first
Read project instructions, manifests, build/test configs, import aliases, package boundaries, generated/vendor rules, CI/deploy files, documentation links, code owners, and dirty-worktree state. Map each proposed move to consumers: imports, scripts, globs, assets, tests, docs, workflows, packaging, and runtime paths.
Classify files as source, tests, configuration, documentation, assets, generated, cache, local-only, secrets, or unknown. Never move/delete an unknown file merely because its name looks untidy.
Plan
Propose the smallest coherent target tree. For each move list source, destination, reason, references to update, collision/case-sensitivity risk, and validation. Respect ecosystem conventions and the repository's established structure; avoid a grand taxonomy that adds empty folders or breaks discoverability.
Apply safely
- Preserve unrelated user changes and create a backup when version control is insufficient.
- Use native filesystem moves within one verified workspace; check case-only renames and Windows path rules.
- Update imports, aliases, manifests, scripts, CI, docs, tests, and ignore rules in the same atomic slice.
- Do not delete generated/cache content unless its regeneration command is verified and deletion is in scope.
- Do not move secrets into tracked paths.
- Keep public APIs and package entry points stable or document a deliberate migration.
Implement in small slices and validate after each risky boundary move. Stop and roll back the slice that causes unexplained behavior changes.
Validation
Run project format/lint/typecheck/build/tests, package/import resolution, startup/smoke tests, docs/link checks, CI config parsing, and a search for stale old paths. Compare file counts and verify no unexpected untracked or missing files. On case-insensitive filesystems, test the final casing explicitly.
Deliverable
Return old/new tree summaries, move map, updated consumers, commands run, validation, remaining compatibility risks, and rollback path. Invocation is by natural-language request or the host's supported skill mechanism; never assume a particular slash command or provider directory.