code-style-analyzer

Included with Lifetime

$97 forever

Analyzes code for style and formatting issues including inconsistent formatting, naming conventions, code organization, comment quality, unused code, and magic numbers. Returns structured style issue reports with suggestions for improvement.

General

What this skill does


# Code Style Analyzer Skill

## Instructions

1. Analyze code for style and formatting issues
2. Check for inconsistent formatting (indentation, spacing, brackets)
3. Verify naming conventions are followed
4. Check code organization and structure
5. Review comment quality and presence
6. Identify unused code (variables, functions, imports)
7. Look for magic numbers and strings
8. Return structured style reports with:
   - File path and line numbers
   - Style issue type
   - Current code
   - Suggested improvement
   - Reason
   - Priority (usually Should-Fix or Nice-to-Have)

## Examples

**Input:** Inconsistent indentation
**Output:**
```markdown
### STYLE-001
- **File**: `index.html`
- **Lines**: 15-20
- **Priority**: Should-Fix
- **Issue**: Inconsistent indentation (mixing tabs and spaces)
- **Current Code**:
  ```html
  <div>
    <p>Text</p>
      <span>More text</span>
  </div>
  ```
- **Suggested Fix**:
  ```html
  <div>
      <p>Text</p>
      <span>More text</span>
  </div>
  ```
- **Reason**: Consistent indentation improves readability and maintainability
```

## Style Issues to Detect

- **Formatting**: Inconsistent indentation, spacing, bracket placement
- **Naming**: Inconsistent naming conventions (camelCase vs snake_case)
- **Code Organization**: Poor file structure, functions in wrong places
- **Comments**: Missing comments, poor comment quality, outdated comments
- **Unused Code**: Unused variables, functions, imports, dead code
- **Magic Numbers/Strings**: Hardcoded values that should be constants
- **Line Length**: Lines that are too long
- **File Length**: Files that are too long
- **Code Duplication**: Repeated code that could be extracted
- **Import Organization**: Unorganized imports

## Priority Guidelines

- **Must-Fix**: Style issues that cause bugs or significant readability problems
- **Should-Fix**: Style issues that affect readability and maintainability
- **Nice-to-Have**: Cosmetic style improvements

Files: 1

Size: 2.2 KB

Complexity: 6/100

Category: General

Source: https://github.com/lexicalninja/my-little-scrum-team/tree/main/skills/code-style-analyzer

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts