d-oitd-oit/rust-2026-template/.agents/skills/codacy/SKILL.md

codacy

Skill15 starsChanged 5 months agoMITView on GitHub

Use Codacy static analysis CLIs to query PR analysis, triage issues, suppress false positives, and run local analysis. Use when Codacy blocks a PR, when asked to fix Codacy issues, suppress false positives, query PR quality data, or integrate Codacy into CI/CD workflows. Also use when the user mentions "Codacy", "static analysis check", "code quality gate", or "Codacy is failing".

Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

d-o-hub/github-template-ai-agentstheir own version, first seen Nov 3, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
d-o-hub/github-template-ai-agents★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- anti-ai-slopSkill
- architecture-diagramSkill
- atomic-commitSkill
- build-rustSkill
- crates-io-name-checkSkill
- dora-reportSkill
- goap-agentSkill
- harnessSkill
- issue-triageSkill
- lint-rustSkill
- metrics-reporterSkill
- privacy-firstSkill
- release-rustSkill
- reviewing-pull-requestsSkill
- secret-lintSkill
- self-fix-loopSkill
- skill-creatorSkill
- skill-evaluatorSkill
- stacked-prsSkill
- task-decompositionSkill
- test-rustSkill
- tokio-performanceSkill
- triz-analysisSkill
- triz-solverSkill
- verify-actionsSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Always cross-reference with Cloud CLI for full PR data.
line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Codacy Static Analysis

Installation & Auth

# Analysis CLI (for local runs)
npm i -g @codacy/analysis-cli

# Cloud CLI (for PR data and suppressions)
npm i -g @codacy/codacy-cloud-cli

export CODACY_API_TOKEN=<your-api-token>

PR Triage Workflow

Get PR analysis: codacy pull-request gh <org> <repo> <prNumber> --output json > /tmp/codacy-pr.json
Categorize issues:
- False positives → Suppress via Cloud CLI.
- Real issues → Fix in code.
Suppress false positives: codacy pull-request gh <org> <repo> <prNumber> --ignore-issue <numeric-resultDataId> --ignore-reason FalsePositive Note: Use numeric resultDataId, NOT hash IDs.
Fix issues: Batch fix patterns and verify with local lint/tests.

Local Analysis

# Initialize configuration (generates .codacy.yml)
codacy-analysis init --default

# Run local analysis
codacy-analysis analyze --pr --output-format json

Known Limitations

Tool Category	Status	Note
JS/TS/Shell	✅ Works	ESLint9, Stylelint, ShellCheck
Rust	⚠️ Limited	Local analysis uses `jscpd` and `Lizard`; Cloud uses `Opengrep`
Python/Ruby	❌ Fails	Missing runtimes/venv issues
Java/PMD	❌ Fails	Missing Java runtime

Always cross-reference with Cloud CLI for full PR data.

Rationalizations

Rationalization	Reality
"Local analysis shows 0 issues, so we are good."	Analysis CLI has limited local tool support; Cloud CLI is the source of truth.
"I'll use the issue hash for suppression."	Codacy CLI requires the numeric `resultDataId` for suppressions.

Red Flags

Relying solely on local codacy-analysis for Rust/Python/Java projects.
Attempting to suppress issues without a valid --ignore-reason.
Ignoring the resultDataId field in JSON output in favor of hashes.

References

references/config-format.md - .codacy.yml schema and advanced options
references/output-format.md - JSON schema for PR analysis
references/supported-tools.md - Local vs Cloud tool availability

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free