Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Static Code Analysis

  • 559 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

static-code-analysis is a Claude Code skill that implements linters, formatters, and security scanners to catch bugs and style violations for developers who need automated analysis before merging or deploying code.

About

static-code-analysis is a skill in aj-geddes/useful-ai-prompts for setting up automated code analysis without execution. It integrates linters, formatters, and security scanners to detect bugs, vulnerabilities, and style violations early in the development cycle. Developers invoke it when enforcing team coding standards, hardening CI pipelines, or augmenting manual code review with repeatable checks. The skill guides agent sessions through tool selection, configuration, and pipeline wiring so analysis runs on every pull request or pre-deploy step. Reach for static-code-analysis when prompts mention ESLint, Prettier, Semgrep, SonarQube, or automated review gates.

  • Catches bugs and security vulnerabilities without running code
  • Enforces consistent coding standards across projects
  • Automates code review in CI/CD pipelines and pre-commit hooks
  • Supports ESLint, TypeScript, security plugins and import ordering
  • Provides actionable warnings and errors for refactoring

Static Code Analysis by the numbers

  • 559 all-time installs (skills.sh)
  • Ranked #226 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill static-code-analysis

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs559
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you set up static analysis in CI pipelines?

Automatically catch bugs, security issues, and style violations before merging or deploying code.

Who is it for?

Developers adding automated linting, formatting, and security scanning gates to CI before merging or deploying application code.

Skip if: Teams needing runtime profiling, load testing, or dynamic penetration testing that requires executing the application in production-like environments.

When should I use this skill?

User asks to set up linters, formatters, security scanners, ESLint, Prettier, or automated code review checks in CI.

What you get

Linter and formatter configs, security scanner integration, and CI pipeline checks that block bugs and style violations pre-merge.

  • Linter and formatter configuration files
  • CI pipeline static analysis job

By the numbers

  • Covers three static analysis tool classes: linters, formatters, and security scanners

Files

SKILL.mdMarkdownGitHub ↗

Static Code Analysis

Table of Contents

Overview

Use automated tools to analyze code without executing it, catching bugs, security issues, and style violations early.

When to Use

  • Enforcing coding standards
  • Security vulnerability detection
  • Bug prevention
  • Code review automation
  • CI/CD pipelines
  • Pre-commit hooks
  • Refactoring assistance

Quick Start

Minimal working example:

// .eslintrc.js
module.exports = {
  extends: [
    "eslint:recommended",
    "plugin:@typescript-eslint/recommended",
    "plugin:security/recommended",
  ],
  plugins: ["@typescript-eslint", "security", "import"],
  rules: {
    "no-console": ["warn", { allow: ["error", "warn"] }],
    "no-unused-vars": "error",
    "prefer-const": "error",
    eqeqeq: ["error", "always"],
    "no-eval": "error",
    "security/detect-object-injection": "warn",
    "security/detect-non-literal-regexp": "warn",
    "@typescript-eslint/no-explicit-any": "warn",
    "@typescript-eslint/explicit-function-return-type": "error",
    "import/order": [
      "error",
      {
        groups: [
          "builtin",
          "external",
          "internal",
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
ESLint ConfigurationESLint Configuration
Python Linting (pylint + mypy)Python Linting (pylint + mypy)
Pre-commit HooksPre-commit Hooks
SonarQube IntegrationSonarQube Integration
Custom AST AnalysisCustom AST Analysis
Security ScanningSecurity Scanning

Best Practices

✅ DO

  • Run linters in CI/CD
  • Use pre-commit hooks
  • Configure IDE integration
  • Fix issues incrementally
  • Document custom rules
  • Share configuration across team
  • Automate security scanning

❌ DON'T

  • Ignore all warnings
  • Skip linter setup
  • Commit lint violations
  • Use overly strict rules initially
  • Skip security scans
  • Disable rules without reason

Related skills

How it compares

Choose static-code-analysis over runtime debugging skills when the goal is pre-merge linting, formatting, and vulnerability scanning without executing code.

FAQ

What does static-code-analysis check without running code?

static-code-analysis configures linters, formatters, and security scanners that analyze source statically. The skill catches bugs, vulnerabilities, and style violations before merge or deployment without executing the application.

When should static-code-analysis run in a workflow?

static-code-analysis fits pre-merge CI gates and pre-deploy checks. Invoke it when enforcing coding standards, automating review, or detecting security issues before shipping changes to production.

Can static-code-analysis replace manual code review?

static-code-analysis augments manual review with repeatable linter, formatter, and scanner checks. It standardizes enforcement across pull requests but does not replace human judgment on architecture or business logic.

Code Review & Qualitytestingintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.