Agent skill · software engineering · aj-geddes
static-code-analysis
Implement static code analysis with linters, formatters, and security scanners to catch bugs early. Use when enforcing code standards, detecting security vulnerabilities, or automating code review.
Why this skill is useful
Provides specific configurations and integration patterns for multiple linters and security scanners that the AI wouldn't reliably generate on its own.
What it needs
Requires eslint, mypy, pylint, sonarqube installed locally. About 1k tokens when loaded. Last updated 2026-03-04. 307 stars on the source repository.
What this skill does
Static Code Analysis Table of Contents Overview When to Use Quick Start Reference Guides Best Practices 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: Reference Guides Detailed implementations in the references/ directory: Guide Contents --- --- ESLint Configuration ESLint Configuration Python Linting (pylint + mypy) Python Linting (pylint + mypy) Pre-commit Hooks Pre-commit Hooks SonarQube Integration SonarQube Integration Custom AST Analysis Custom AST Analysis Security Scanning Security 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
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/static-code-analysis