codacy-audit

Automate local static analysis and PR issue triage for Codacy-monitored repositories.

80.4k|6.6k|Updated Jun 17, 2013
One-click install
npx skills add https://github.com/netdata/netdata --skill codacy-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codacy-audit
Source: https://github.com/netdata/netdata/tree/main/.agents/skills/codacy-audit
Command: npx skills add https://github.com/netdata/netdata --skill codacy-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, docker, codacy-analysis-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates the feedback loop delay between pushing code and seeing static analysis results, while providing a structured way to triage existing technical debt on pull requests.

Core Features & Use Cases

  • Pre-push Analysis: Run the same analyzers locally that Codacy CI uses to catch issues before they reach the server.
  • PR Issue Triage: Fetch and cluster Codacy issues for any pull request to prioritize fixes by tool, pattern, or severity.
  • Use Case: When a developer receives a Codacy gate failure on a PR, they can use this skill to reproduce the findings locally, fix them, and verify the resolution before pushing again.

Quick Start

Run the codacy-audit skill to analyze the current directory and list any findings before pushing your changes.

Frequently Asked Questions about codacy-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Codacy analysis locally before pushing?

Use the analyze-local.sh script to execute the Codacy CLI against your working tree. It automatically detects if you have the local binary or Docker installed and writes a JSON dump of findings to your local audit directory.

How can I see Codacy issues for a specific PR?

Use the pr-issues.sh script followed by the PR number to fetch all issues via the Codacy v3 API. The script clusters findings by tool, pattern, or severity to help you prioritize your work.

Why does my local analysis output contain logs instead of JSON?

This happens when the Dockerized CLI fails to read files or encounters environment issues. Verify the output with 'jq empty' and check the first few lines of the file to identify the specific runner error.

Is it safe to use my Codacy API token with this skill?

Yes, the skill is designed to be token-safe. It uses internal wrappers that prevent the CODACY_TOKEN from being echoed to stdout or committed to any files, and includes a self-test to verify no leaks occur.