원클릭으로 Manus에서 모든 스킬 실행

$pwd:

cleanup-legacy

Name: Cleanup Legacy
Author: raintree-technology

// Find and remove deprecated, legacy, and fallback code paths with zero callers. Verifies callers via repo grep + LSP before deletion. Removes unreachable fallback branches. Use when the user asks to remove deprecated code, clean up legacy paths, drop fallbacks, or simplify code branches. Example queries — "remove the deprecated API", "drop the v1 fallback", "this code is marked legacy, kill it", "simplify these branches".

Manus에서 실행

$ git log --oneline --stat

stars:76

forks:8

updated:2026년 4월 24일 22:43

SKILL.md

readonly

related-skills.json

같은 저장소

cleanup-all.md

from "raintree-technology/claude-starter"

Run all 8 cleanup skills in sequence: unused → cycles → dedupe → types → weak-types → defensive → legacy → slop. Each step verifies before the next runs; halts on first failure. Produces one consolidated report. Use when the user asks to clean up the whole codebase, run all cleanup skills, do a full code-quality pass, or sweep the repo. Example queries — "clean up the whole codebase", "run a full code-quality pass", "sweep this repo", "do all the cleanups in order".

2026-04-2476

cleanup-cycles.md

from "raintree-technology/claude-starter"

Detect and untangle circular dependencies. Runs madge/skott (TS), pycycle (Py), or compiler-only checks (Go/Rust). Auto-fixes leaf-extractable cycles; reports core cycles for human review. Use when the user asks to find circular imports, fix dependency cycles, or untangle module graph. Example queries — "find circular imports", "fix dependency cycles", "untangle our module graph", "why is madge complaining".

2026-04-2476

cleanup-dedupe.md

from "raintree-technology/claude-starter"

Detect duplicated code blocks and refactor to DRY where it reduces complexity. Runs jscpd (multi-language), filters by signal-to-noise, and auto-extracts only token-identical blocks ≥30 LOC. Use when the user asks to deduplicate, DRY up, find copy-paste, or consolidate repeated logic. Example queries — "DRY this up", "find copy-paste in the codebase", "consolidate repeated logic", "where are the duplicated blocks".

2026-04-2476

cleanup-defensive.md

from "raintree-technology/claude-starter"

Remove pointless try/catch blocks and defensive guards that hide errors or add no value. Preserves catches at true system boundaries (HTTP handlers, CLI entry, message consumers). Use when the user asks to remove try/catch, fix error hiding, clean up defensive code, or stop swallowing errors. Example queries — "remove pointless try/catch", "we're swallowing errors", "stop hiding bugs in catch blocks", "clean up the defensive code".

2026-04-2476

cleanup-slop.md

from "raintree-technology/claude-starter"

Strip AI slop, narration comments, restated-code comments, in-motion notes, and stub markers. Preserves comments that explain WHY (workarounds, invariants, surprising behavior). Comment-only changes — never touches code logic. Use when the user asks to remove AI slop, clean up comments, strip narration, or remove unhelpful comments. Example queries — "remove the AI slop", "strip the narration comments", "clean up unhelpful comments", "delete the comments that just restate the code".

2026-04-2476

cleanup-types.md

from "raintree-technology/claude-starter"

Find duplicated or fragmented type/interface definitions across files and consolidate to a shared types module. TypeScript-first; also handles Python dataclasses/TypedDicts and Go structs. Use when the user asks to consolidate types, find duplicate interfaces, or organize type definitions. Example queries — "consolidate our types", "find duplicate interfaces", "this same type is defined in three files", "organize the type definitions".

2026-04-2476

package.json

"author": "raintree-technology"

"repository": "raintree-technology/claude-starter"

GitHub 저장소 열기 Creator 저장소 보기

$ install --global

$ download --local

Manus에서 실행

$ useful --forSOC

소프트웨어 개발자컴퓨터 및 수학직15-1252L4

grep -rn --include="*.ts" --include="*.tsx" --include="*.js" --include="*.py" --include="*.go" --include="*.rs" \ -E "(@deprecated|# ?deprecated|// ?Deprecated|#\[deprecated|warnings\.warn.*Deprecation|TODO.*remove|FIXME.*legacy)" \ --exclude-dir=node_modules --exclude-dir=dist . > /tmp/deprecated.txt # Files/dirs with legacy naming find . -type d $ -name "legacy" -o -name "old" -o -name "v1" -o -name "_archive" $ -not -path "*/node_modules/*" > /tmp/legacy-dirs.txt find . -type f $ -name "*_old.*" -o -name "*-legacy.*" -o -name "*.deprecated.*" $ > /tmp/legacy-files.txt

# Legacy Code Assessment — YYYY-MM-DD ## Summary - Deprecated symbols found: N - HIGH (zero callers): X — safe to delete - MEDIUM (1-5 callers): Y — needs migration - LOW (heavy use): Z — deprecated in name but actively used - Legacy directories: M - Dead fallback branches: K ## Findings ### HIGH — `packages/utils/src/format-old.ts` - Marked `@deprecated` since commit abc123 (2024-08-15). - Exports: `formatV1`, `parseV1`. Repo grep shows zero usages outside the file. - Action: delete file. ### HIGH — `apps/app/lib/feature-flags.ts:45-60` - Branch: `if (NEW_DASHBOARD_ENABLED) { ... } else { renderOldDashboard() }`. - Flag is `true` in all envs (`.env`, `.env.staging`, `.env.production`) and has been for 6+ months per git log. - Action: remove the else branch + the flag check + the `renderOldDashboard` function (cascade). ### MEDIUM — `domains/billing/legacy.ts` - 8 callers across 3 packages. - Marked deprecated 3 months ago. Migration path documented in inline comment to use `domains/billing/v2`. - Recommendation: do NOT delete. Provide a migration list to the human; this needs sequencing. ### LOW — `lib/utils/oldHelper.ts` - Marked `@deprecated` but has 47 active callers. - Either the deprecation is aspirational with no migration plan, or it was incorrectly marked. Flag for human review of the deprecation. ## Critical Assessment [2-3 paragraphs: what's the pattern of deprecation in this codebase? Are deprecations followed by deletion? Are there feature flags that should have been cleaned up months ago? Are "legacy" directories accumulating but not draining?]

bun run check 2>&1 || npx tsc --noEmit && npx eslint . bun test 2>&1 pytest 2>&1 go test ./... 2>&1 cargo test 2>&1 # If knip is installed, run it — newly-orphaned exports may surface bunx knip 2>&1 || true

cleanup-legacy

Preflight

Detect

Marker grep (multi-language)

Caller verification (TS/JS)

Caller verification (Python)

Fallback branches

Assess

Apply

Confidence rubric

Execution (HIGH only)

Verify

Output

NEVER

Preflight

Detect

Marker grep (multi-language)

Caller verification (TS/JS)

Caller verification (Python)

Fallback branches

Assess

Apply

Confidence rubric

Execution (HIGH only)

Verify

Output

NEVER

name	cleanup-legacy
description	Find and remove deprecated, legacy, and fallback code paths with zero callers. Verifies callers via repo grep + LSP before deletion. Removes unreachable fallback branches. Use when the user asks to remove deprecated code, clean up legacy paths, drop fallbacks, or simplify code branches. Example queries — "remove the deprecated API", "drop the v1 fallback", "this code is marked legacy, kill it", "simplify these branches".
argument-hint	[scope (optional path or glob)]
user-invocable	true

cleanup-legacy

이 저장소의 다른 Skills

이 저장소의 다른 Skills

Preflight

Detect

Marker grep (multi-language)

Caller verification (TS/JS)

Caller verification (Python)

Fallback branches

Assess

Apply

Confidence rubric

Execution (HIGH only)

Verify

Output

NEVER

Preflight

Detect

Marker grep (multi-language)

Caller verification (TS/JS)

Caller verification (Python)

Fallback branches

Assess

Apply

Confidence rubric

Execution (HIGH only)

Verify

Output

NEVER