clean-up-wrong-path-immediately

Estrellas9

Forks0

Actualizado8 de julio de 2026 a las 21:55

When files are accidentally created in the wrong directory, remove them immediately before proceeding to the correct location.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

surenode-ai

surenode-ai/skill-extractor

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	clean-up-wrong-path-immediately
description	When files are accidentally created in the wrong directory, remove them immediately before proceeding to the correct location.

Immediately Clean Up Files Written to Wrong Location

When to use: When you realize you've written files to the wrong project directory or path.

Rule

As soon as you realize a file was created in the wrong location, immediately delete it before doing anything else.
Use rm -f <file> and rmdir <dir> to clean up.
Confirm cleanup with an echo/message.
Only then proceed to the correct location.

Why: Stray files in wrong repos cause confusion, potential git commits of garbage, and clutter. The longer they exist, the more likely they'll be forgotten.

Prevention: Before writing files, confirm the correct project root by checking for existing project markers (package.json, README, .git, existing index.html).

Mined by skill-extractor from a local repo (confidence 0.7, utility 0.629, trace outcome success). Review & edit as needed.

Más de este repositorio

mismo repositorio

match-existing-design-system-before-editing

surenode-ai/skill-extractor

Before adding new UI elements to an existing site, read the stylesheet to extract design tokens (colors, radii, font, button classes) so new elements look native.

2026-07-089

verify-baseline-before-changes

surenode-ai/skill-extractor

Before implementing new features, run existing tests to confirm green baseline: this ensures any failures after changes are attributable to new code, not pre-existing issues.

2026-07-089

review-skills

surenode-ai/skill-extractor

Review skills that the skill-extractor mined from your Claude Code traces — inspect each candidate's definition and confidence/utility scores, edit it, then install it as a real skill or reject it with a comment. Use when the user runs /review-skills, asks to "review discovered/mined skills", or a session-start banner reports pending skills.

2026-07-079

name	clean-up-wrong-path-immediately
description	When files are accidentally created in the wrong directory, remove them immediately before proceeding to the correct location.

Immediately Clean Up Files Written to Wrong Location

When to use: When you realize you've written files to the wrong project directory or path.

Rule

As soon as you realize a file was created in the wrong location, immediately delete it before doing anything else.
Use rm -f <file> and rmdir <dir> to clean up.
Confirm cleanup with an echo/message.
Only then proceed to the correct location.

Why: Stray files in wrong repos cause confusion, potential git commits of garbage, and clutter. The longer they exist, the more likely they'll be forgotten.

Prevention: Before writing files, confirm the correct project root by checking for existing project markers (package.json, README, .git, existing index.html).

Mined by skill-extractor from a local repo (confidence 0.7, utility 0.629, trace outcome success). Review & edit as needed.