Configure Codacy

Glossary: See glossary.md for shared definitions of Codacy concepts (issues, findings, severity, coverage, tools, patterns, etc.).

This skill tailors Codacy configuration to a project's actual stack and coding conventions. It discovers the repository's languages and frameworks, initializes a broad set of tools and patterns, runs analysis, then intelligently cuts noise — producing a clean, high-signal configuration with a full audit trail of what changed and why.

Prerequisites

• Codacy Analysis CLI (codacy-analysis) with discover and init --auto support. If the CLI does not support these commands, update it running: npm i -g @codacy/analysis-cli. See codacy-analysis-cli for setup.
• Codacy Cloud CLI (codacy) — needed to know if the repo is on Codacy Cloud and if so, fetch issues from the cloud-only tools. See codacy-cloud-cli for setup.

Both CLIs share credentials at ~/.codacy/credentials, so a single login covers both.

How configuration works

All configuration is done locally via .codacy/codacy.config.json. Edit the file, run analysis, see results instantly — no push or cloud reanalysis needed. Once tuned, the configuration can be imported to Codacy Cloud in one step.

The key principle: start broad, then cut noise using data. Initialize with maximum pattern coverage via init --auto, run analysis to see the full issue landscape, then use the severity/category distribution to decide what to disable or tune.