Code Quality Hint
Notices code quality issues when viewing code with long functions, deep nesting, duplicated code, unclear naming, or obvious anti-patterns. Use when user shows code that might benefit from refactoring or has maintainability concerns.
What this skill does
# Code Quality Hint Lightweight code quality awareness for conversations. Provides quick hints about maintainability issues without full review. ## When to activate Activate when you notice in code being discussed: - Functions longer than 50-60 lines - Nesting deeper than 3 levels - Duplicated code blocks - Unclear variable names (x, data, temp, result) - Missing error handling - TODO/FIXME comments - Commented-out code - Magic numbers without explanation - Callback hell - Large switch statements ## What to do **Briefly mention** the concern in 1-2 sentences, then suggest running a command: **Example responses:** ``` "This function is quite long (80+ lines). Consider splitting it for better maintainability. Run `/review src/service.js` for refactoring suggestions." ``` ``` "I see duplicated logic on lines 23-35 and 78-90. Run `/quick-check` to identify code quality improvements." ``` ``` "Variable names like 'x', 'temp', and 'data' make this code hard to follow. Run `/deep-review` for comprehensive code quality analysis and best practices." ``` ## Important rules - ❌ Do NOT perform full code review - ❌ Do NOT refactor code automatically - ✅ Only mention clear issues in current conversation - ✅ Keep hints brief (1-2 sentences) - ✅ Always suggest a command for detailed review - ✅ Be constructive, not critical ## Common patterns to flag **Function size:** - Functions > 50 lines (suggest splitting) - Functions doing multiple things **Nesting:** - More than 3 levels deep - Early returns could flatten structure **Naming:** - Single letter variables (except loop counters) - Generic names (data, result, temp, x) - Inconsistent naming conventions **Code smells:** - Duplicated blocks - God functions/classes - Long parameter lists - Commented-out code - console.log in production code **Error handling:** - Missing try-catch - Swallowed errors - No input validation ## What NOT to flag - Style preferences (tabs vs spaces) - Formatting (handled by formatters) - Minor optimizations - Subjective choices ## Commands to suggest - `/quick-check` - for fast quality check - `/review [file]` - for specific file analysis - `/deep-review` - for comprehensive quality review with Context7 (checks against current best practices) This is a hint tool to improve awareness during normal coding conversations.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.