repo-cleanup-folders-to-delete-confirmed-safe

Sub-skill of repo-cleanup: Folders to DELETE (Confirmed Safe) (+3).

5 stars

Best use case

repo-cleanup-folders-to-delete-confirmed-safe is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of repo-cleanup: Folders to DELETE (Confirmed Safe) (+3).

Teams using repo-cleanup-folders-to-delete-confirmed-safe should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/folders-to-delete-confirmed-safe/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_internal/meta/repo-cleanup/folders-to-delete-confirmed-safe/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/folders-to-delete-confirmed-safe/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How repo-cleanup-folders-to-delete-confirmed-safe Compares

Feature / Agentrepo-cleanup-folders-to-delete-confirmed-safeStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Sub-skill of repo-cleanup: Folders to DELETE (Confirmed Safe) (+3).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Folders to DELETE (Confirmed Safe) (+3)

## Folders to DELETE (Confirmed Safe)


| Folder | Reason | Verification |
|--------|--------|--------------|
| `.drcode/` | Legacy AI config (Dr. Code) | Not referenced in any scripts or CI |
| `.benchmarks/` | Empty benchmark folder | `ls .benchmarks/` returns empty or missing |
| `.agent-runtime/` | Dead symlinks only | `find .agent-runtime -type l ! -exec test -e {} \;` |
| `.common/` | Orphaned utilities | No imports reference this folder |
| `.specify/` | Stale specification templates | Specs moved to `specs/templates/` |

## Folders to CONSOLIDATE


| Source | Destination | Command |
|--------|-------------|---------|
| `.slash-commands/` | `.Codex/docs/commands/` | `git mv .slash-commands/* .Codex/docs/commands/` |
| `.git-commands/` | `scripts/git/` | `git mv .git-commands/* scripts/git/` |
| `.agent-os/` | `.Codex/` | See module-based-refactor skill |
| `.ai/` | `.Codex/` | See module-based-refactor skill |

## Folders to KEEP


| Folder | Reason |
|--------|--------|
| `.githooks/` | Standard location for git hooks |
| `.github/` | GitHub workflows and templates |
| `.Codex/` | Authoritative AI configuration |
| `.vscode/` | Team VS Code settings (if tracked) |

## Cleanup Commands


```bash
# Delete legacy config folders
rm -rf .drcode/
rm -rf .benchmarks/

# Consolidate slash-commands to docs
mkdir -p .Codex/docs/commands
git mv .slash-commands/* .Codex/docs/commands/ 2>/dev/null
rm -rf .slash-commands/


*See sub-skills for full details.*

Related Skills

interactive-report-generator

5
from vamseeachanta/workspace-hub

Generate interactive HTML reports with Plotly visualizations from data analysis results. Supports dashboards, charts, and professional styling.

data-validation-reporter

5
from vamseeachanta/workspace-hub

Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.

repo-ecosystem-hygiene

5
from vamseeachanta/workspace-hub

Interpret the daily read-only repo ecosystem hygiene audit and route remediation through approved workflows.

mnt-analysis-cleanup

5
from vamseeachanta/workspace-hub

Survey, classify, and clean up `/mnt/local-analysis/` (or any sibling-to-workspace-hub directory holding orphan worktrees, codex-burn artifacts, agent log accumulations, and outer-clone duplicates) without losing useful code/work. Surfaces a tiered approval menu rather than baking decisions; defers all destructive ops until user confirms.

orcaflex-reporting-fixture-proof-pattern

5
from vamseeachanta/workspace-hub

Build and extend fixture-backed OrcaFlex reporting proof paths in digitalmodel using stable metadata baselines, normalized HTML snapshots, and reusable reporting test helpers.

marine-safety-incidents

5
from vamseeachanta/workspace-hub

Collect, analyze, and report marine safety incident data from 7 global maritime authorities. Use for incident scraping, safety trend analysis, risk assessment, geographic hotspot identification, and marine safety reporting.

pre-completion-cleanup-audit

5
from vamseeachanta/workspace-hub

Audit and dispose of session residue (orphan files, scratch dirs, sibling-repo state, locks, trash-stages) BEFORE claiming a task complete. Required gate before any agent says "all done", "task complete", or hands work back to user/orchestrator.

repo-sync

5
from vamseeachanta/workspace-hub

Smart repository synchronization across workspace-hub ecosystem — diagnoses and fixes pull failures (detached HEAD, diverged branches, uncommitted changes)

repo-structure

5
from vamseeachanta/workspace-hub

Canonical source layout, test mirroring, root cleanliness, gitignore, docs classification, and committed artifact rules for all workspace-hub tier-1 repos. Consult before creating directories or files in any submodule.

repo-portfolio-steering

5
from vamseeachanta/workspace-hub

Generate a one-page portfolio steering report for workspace-hub. Use when the user invokes /repo-portfolio-steering, asks about harness vs engineering balance, wants a portfolio health check, or asks which repos to fund next. Reports on portfolio steering, GTM readiness, and provider activity balance.

repo-mission-portfolio-audit

5
from vamseeachanta/workspace-hub

Audit the workspace-hub repo portfolio to extract each repo's mission, identify documentation gaps, and prioritize a plan/approval sequence with explicit LLM-wiki weighting for future issue triage.

mixed-ops-vs-repo-fix-plan-boundary

5
from vamseeachanta/workspace-hub

Plan mixed operational-vs-repo remediation issues by proving live-state classification first, then only proposing code changes for confirmed repo-owned failure paths.