Skip to content

Commit a23378b

Browse files
finish first iteration
1 parent c93035f commit a23378b

1 file changed

Lines changed: 2 additions & 8 deletions

File tree

docs/codacy-guardrails/codacy-guardrails-how-to-use.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
1. Let's run an prompt to create a webserver in Java
66

7-
```bash
7+
```text
88
Create a lightweight webserver in Java.
99
```
1010

@@ -14,7 +14,6 @@ In response, it generated a compact, readable Java class using ServerSocket and
1414

1515
![response to the webserver creation using AI](images/response-webserver.png)
1616

17-
1817
2. There's a call from MCP tool to analyse the code that was generated. Click in **Run tool**
1918

2019
Codacy Guardrails starts analyzing it automatically using the Codacy CLI embedded in the agent’s flow. No configs, no extra steps – it just works.
@@ -33,13 +32,12 @@ Once your repository is connected to Codacy, you can go beyond traditional stati
3332

3433
1. Let's run a quick example with the prompt:
3534

36-
```bash
35+
```text
3736
Can you tell what security issues I have in my repository?
3837
```
3938

4039
![Prompt list the security issues in my repository](images/prompt-list-security-issues-repository.png)
4140

42-
4341
2. Right after running this prompt, there is a MCP tool call to search all security issues in my repository. Click in **Run tool**
4442

4543
![List the security issues in my repository](images/run-mcp-tool-list-security-issues.png)
@@ -49,7 +47,3 @@ It will search for all open security issues in my repository. And it will list a
4947
![List the security issues in my repository](images/list-security-issues.png)
5048

5149
It turned security from a checklist into a dialogue — and that changes everything.
52-
53-
54-
## Local scanning
55-

0 commit comments

Comments
 (0)