cf-dev-toolkit

Plugin cf-dev-toolkit from marketplace cf-dev-toolkit in rubenCodeforges/codeforges-claude-plugin. Commands read from the repo's manifest — 1 month ago.

Slash commands (5)

• /cf-dev-toolkit:analyze-file

  Deep analysis of a specific file using code-analyst sub-agent

• /cf-dev-toolkit:check-web-perf

  Diagnostic command to check web performance toolkit setup and dependencies

• /cf-dev-toolkit:diagnose-runtime
• /cf-dev-toolkit:map-class-usage

  Build comprehensive usage map for a class showing all methods and fields with their usages

• /cf-dev-toolkit:scan-codebase

  Comprehensive codebase scan and structure mapping

Subagents (9)

• api-analyzer

  MUST BE USED for API analysis. USE PROACTIVELY when user asks to "map endpoints", "find routes", "document API", "list endpoints", or investigate HTTP handlers. Works across frameworks (Express, FastAPI, Django, Spring, Go).

• code-analyst

  MUST BE USED for code file analysis. Performs deep analysis of architecture, patterns, dependencies, complexity, issues, and recommendations. USE PROACTIVELY when user asks to analyze, understand, review, investigate, rework, improve, or check any code file, module, README, or documentation.

• code-scanner

  MUST BE USED for codebase overview. USE PROACTIVELY when user asks to "scan codebase", "show structure", "what's in this project", "tech stack", or needs overall project understanding. Maps directories, detects technologies, analyzes organization.

• dependency-analyzer

  MUST BE USED for dependency analysis. USE PROACTIVELY when user asks about "dependencies", "circular deps", "security vulnerabilities", "bundle size", "npm audit", or package issues. Supports npm, pip, go modules, maven, cargo, composer.

• git-analyzer

  MUST BE USED for git analysis. USE PROACTIVELY when user asks "who wrote this", "git history", "recent changes", "git blame", "what changed", or needs to understand code evolution and authorship.

• performance-analyzer

  MUST BE USED for code performance issues. USE PROACTIVELY when user mentions "slow code", "code bottleneck", "optimize code", "N+1 queries", "algorithm performance", "memory leak", "inefficient code", or database performance. Identifies algorithmic issues, database problems, memory leaks, and code o

• usage-finder

  MUST BE USED for finding code usages and building usage maps. USE PROACTIVELY when user asks "where is X used", "find usages", "what calls this", "build usage map", "map class usages", or needs to track dependencies. Expert at finding functions, methods, classes, variables across codebases and gener

• web-performance-agent

  MUST BE USED for website/page performance analysis. USE PROACTIVELY when user provides a URL to analyze, mentions "lighthouse", "page speed", "web vitals", "website performance", "site performance", "slow loading", "performance audit", "core web vitals", "LCP", "FCP", "page load time", "app freeze",

• web-visual-qa

  MUST BE USED for web application visual testing, UI verification, and screenshot-based debugging. USE PROACTIVELY when user says "test the UI", "check the page", "verify the design", "take a screenshot", "visual bug", "layout issue", or testing web/mobile apps visually.