static-code-analysis

Static Code Analysis Skill

Step 1 — Detect Language and Choose Tool

If a tool is already present, audit its configuration before making changes. Do not replace an established ESLint setup with Rslint unless migration is part of the task or the repo has no rules that Rslint cannot cover yet.

Step 2 — Configure Rules

Apply a strict baseline. If you use import/* rules, ensure eslint-plugin-import is installed and configured.

TypeScript (Rslint)

pnpm add -D @rslint/core
pnpm exec rslint --init

Use pnpm lint as the project script. For repositories that want lint and type checking in one pass, configure parser projects and use:

pnpm exec rslint --type-check .

TypeScript (ESLint fallback)

{
  "rules": {
    "@typescript-eslint/no-explicit-any": "error",
    "@typescript-eslint/no-unused-vars": "error",
    "import/no-commonjs": "error",
    "no-console": "warn",
    "eqeqeq": ["error", "always"]
  }
}

Go (golangci-lint)

linters:
  enable:
    - errcheck
    - gosimple
    - govet
    - ineffassign
    - staticcheck
    - unused
linters-settings:
  govet:
    enable-all: true

Python (Ruff)

[tool.ruff]
select = ["E", "F", "I", "N", "UP", "S", "B"]
ignore = []
line-length = 100

Step 3 — Integrate with CI

Add a lint job that runs before tests and fails on any error (exit code 1):

# .github/workflows/ci.yml
lint:
  runs-on: ubuntu-latest
  steps:
    - uses: actions/checkout@v4
    - name: Run linter
      run: <lint-command>   # e.g., pnpm lint, golangci-lint run, ruff check .