techdebt
Find and fix technical debt including duplicated code, dead code, outdated patterns, and code smells. Run at the end of sessions to clean up.
What this skill does
# Technical Debt Finder Identify and fix technical debt in the codebase. ## What to Look For ### Code Duplication - Functions with similar logic that could be consolidated - Copy-pasted code blocks - Repeated patterns that should be abstracted ### Dead Code - Unused imports - Unused functions or classes - Commented-out code blocks - Unreachable code paths ### Outdated Patterns - Deprecated API usage - Old-style string formatting (% or .format) vs f-strings - Type hints using `typing.List` instead of `list` - Missing type hints on public functions ### Code Smells - Functions longer than 50 lines - Too many parameters (more than 5) - Deep nesting (more than 3 levels) - Magic numbers without constants - Overly complex conditionals ### Missing Best Practices - Missing docstrings on public functions - Missing error handling - Hardcoded values that should be config - Missing tests for critical paths ## Workflow 1. **Scan the Codebase** - Look for patterns matching the issues above - Prioritize by impact and ease of fix 2. **Report Findings** - List issues by category - Include file paths and line numbers - Estimate severity (high/medium/low) 3. **Fix Issues** - Start with high-severity, easy fixes - Create atomic commits for each fix - Run tests after each change 4. **Verify** - Run linter: `ruff check .` - Run tests: `pytest` - Ensure no new issues introduced ## Arguments Optionally specify a directory or file to focus on. Usage: - `/techdebt` - Scan entire project - `/techdebt src/` - Scan specific directory - `/techdebt src/utils.py` - Scan specific file ## Output Provide a summary of: - Issues found (by category) - Issues fixed - Remaining items for future sessions
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.