You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/instructions/codacy.instructions.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,6 +65,7 @@ Configuration for AI behavior when interacting with Codacy's MCP Server
65
65
- "Propose fixes" means to both suggest and, if possible, automatically apply the fixes.
66
66
- You MUST NOT wait for the user to ask for analysis or remind you to run the tool.
67
67
- Do not run `codacy_cli_analyze` looking for changes in duplicated code or code complexity metrics.
68
+
- Complexity metrics are different from complexity issues. When trying to fix complexity in a repository or file, focus on solving the complexity issues and ignore the complexity metric.
68
69
- Do not run `codacy_cli_analyze` looking for changes in code coverage.
69
70
- Do not try to manually install Codacy CLI using either brew, npm, npx, or any other package manager.
70
71
- If the Codacy CLI is not installed, just run the `codacy_cli_analyze` tool from Codacy's MCP Server.
0 commit comments