code-quality-analyzer
Static code analysis, technical debt assessment, engineering velocity metrics
What this skill does
# Code Quality Analyzer ## Overview The Code Quality Analyzer skill provides detailed code-level analysis for technical due diligence. It performs static code analysis, assesses technical debt, and evaluates engineering team velocity to understand code health and development productivity. ## Capabilities ### Static Code Analysis - Run automated code quality checks - Identify code smells and anti-patterns - Measure code complexity metrics - Detect potential bugs and vulnerabilities ### Technical Debt Assessment - Quantify technical debt backlog - Identify high-priority refactoring needs - Assess test coverage and quality - Evaluate documentation completeness ### Engineering Velocity Metrics - Measure deployment frequency - Track lead time for changes - Analyze cycle time and throughput - Assess sprint velocity trends ### Code Health Indicators - Analyze code churn patterns - Review pull request metrics - Assess code review practices - Evaluate dependency management ## Usage ### Analyze Code Quality ``` Input: Repository access, analysis parameters Process: Run static analysis, aggregate metrics Output: Code quality report, issue summary ``` ### Assess Technical Debt ``` Input: Codebase access, debt categorization Process: Inventory debt, estimate remediation Output: Technical debt assessment, prioritization ``` ### Measure Engineering Velocity ``` Input: Git history, project management data Process: Calculate velocity metrics Output: Velocity report, trend analysis ``` ### Review Code Health ``` Input: Repository data, team practices Process: Analyze patterns, compare benchmarks Output: Code health scorecard, recommendations ``` ## Key Metrics | Metric | Description | Target Range | |--------|-------------|--------------| | Test Coverage | % of code covered by tests | 70-90% | | Code Complexity | Cyclomatic complexity average | < 10 | | Tech Debt Ratio | Debt remediation time / dev time | < 5% | | Deployment Frequency | Deployments per week | Daily to weekly | | Change Failure Rate | % of deployments causing issues | < 15% | ## Integration Points - **Technical Due Diligence**: Detailed code analysis for DD - **Tech Stack Scanner**: Complement architecture review - **Technical Assessor (Agent)**: Support agent analysis - **IP Patent Analyzer**: Code-level IP assessment ## Analysis Tools Integration - SonarQube for code quality - CodeClimate for maintainability - GitHub/GitLab analytics - Jira/Linear for velocity data - Custom scripts for specific checks ## Best Practices 1. Calibrate expectations by company stage 2. Focus on trends over absolute numbers 3. Consider context of rapid iteration 4. Balance debt against velocity needs 5. Assess relative to team size and resources
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.