القائمة
Find technical debt patterns in codebases. Use when asked to find duplicated code, inconsistent patterns, or refactoring opportunities.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | techdebt-finder |
| description | Find technical debt patterns in codebases. Use when asked to find duplicated code, inconsistent patterns, or refactoring opportunities. |
| metadata | {"last_updated":"2026-05-10","verified_against":"current local skill refresh"} |
Identify duplicated code, inconsistent patterns, and refactoring opportunities. Prefer pnpx fallow when available for deeper static analysis; use this skill to interpret, prioritize, and turn findings into a practical refactor plan.
pnpx fallow when available, then supplement with targeted grep/search| Debt Type | Detection Method |
|---|---|
| Duplicated code | Hash-compare function bodies |
| Similar-but-diff | Fuzzy match on structure |
| Inconsistent naming | Regex for mixed conventions |
| Dead code | Unreferenced exports/functions |
| Deferred-work notes | Grep for comment markers |
| Magic numbers | Literals outside const/config |
| Long functions | Line count > threshold |
| Deep nesting | Indentation level analysis |
## Technical Debt Report
### High Priority (fix soon)
- [DUPLICATE] src/utils/format.ts:23 ↔ src/helpers/fmt.ts:45
Similar: 87% | Impact: High (called 12 places)
### Medium Priority (plan for)
- [INCONSISTENT] Mixed naming: getUserData vs fetch_user
Files: api.ts, service.ts, handler.ts
### Low Priority (track)
- [DEFERRED] 23 deferred-work comments, oldest: 2023-01-15
Coordinate parallel agent work. Use when decomposing complex tasks, running review/implementation in parallel, managing task lists, or choosing shared vs isolated workspaces.
Svelte deployment guidance. Use for adapters, Vite config, pnpm setup, library authoring, PWA, or production builds.
SvelteKit data flow guidance. Use when working with load functions, form actions, server/client boundaries, serialization, or invalidation.
Implement SvelteKit remote functions. Use for query(), query.live(), form(), command(), and prerender() patterns in .remote.ts files.
SvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.
Svelte 5 core best practices. Use when creating, editing, or reviewing .svelte, .svelte.ts, or .svelte.js files. Routes to deeper Svelte skills.