Configure Codacy (Cloud)

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

This skill tunes the Codacy configuration of a repository directly on Codacy Cloud, using the cloud as the source of truth. It does not run local analysis. It reads the current cloud issue landscape, applies a higher-signal set of tools and patterns, reanalyzes on Codacy, and iteratively cuts noise over two passes — producing a clean, high-signal configuration with a full audit trail of what changed and why.

For the local-first variant that discovers a stack from scratch and runs codacy-analysis analyze locally, use the configure-codacy skill instead. This skill is for repositories already on Codacy with a finished analysis where you want to tune the cloud config in place.

Prerequisites and requirements

• Codacy Cloud CLI (codacy) — drives all cloud reads, updates, and reanalysis. See codacy-cloud-cli for setup.
• Codacy Analysis CLI (codacy-analysis) — used only for config-file operations (init --remote, init --auto, config --merge). See codacy-analysis-cli for setup.
• Both CLIs share credentials at ~/.codacy/credentials, so a single login covers both.

This skill has three hard requirements. Verify all three before doing anything else and stop with clear guidance if any fails: