checkmarx-devassist-asca

Scans source code files with Checkmarx ASCA SAST and remediates findings via the Checkmarx MCP.

2|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/Checkmarx/cx-agentic-ai --skill checkmarx-devassist-asca-checkmarx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkmarx-devassist-asca
Source: https://github.com/Checkmarx/cx-agentic-ai/tree/main/plugins/copilot-devassist/skills/checkmarx-devassist-asca
Command: npx skills add https://github.com/Checkmarx/cx-agentic-ai --skill checkmarx-devassist-asca-checkmarx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Source code files often contain security vulnerabilities like unsafe subprocess calls or injection flaws that go unnoticed until late in development. This Skill runs a Checkmarx ASCA SAST scan on individual source files and remediates confirmed findings through the Checkmarx MCP, so vulnerabilities are detected and fixed directly in the AI-assisted workflow. ## Core Features & Use Cases - On-Demand SAST Scanning: Runs cx scan asca on source files (.py, .js, .java, .go, .ts, etc.) and reports each finding with rule name, severity, line, description, and remediation advice. - MCP-Driven Remediation: Applies fixes exclusively through the mcp__Checkmarx__codeRemediation tool, then re-scans to verify the fix and distinguish in-scope findings from pre-existing ones. - Fail-Closed Recovery: If the Checkmarx MCP is unavailable, the Skill stops rather than improvising a manual fix, and guides authentication validation and MCP reconnection. - Use Case: A developer asks the assistant to scan app.py for security issues; the Skill reports a High-severity unsafe shell=True subprocess call on line 38, remediates it via the Checkmarx MCP, re-scans, and outputs a structured remediation summary. ## Quick Start Ask the assistant to scan a source code file such as app.py for security vulnerabilities and remediate any findings.

Frequently Asked Questions about checkmarx-devassist-asca

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

FAQPage Schema
How do I scan a source code file for vulnerabilities with Checkmarx?

Run the Checkmarx cx CLI with `cx scan asca -s <file-path>` on the target source file. The scan returns JSON findings with rule name, severity, line number, description, and remediation advice for each detected vulnerability.

What is the difference between Checkmarx ASCA and SCA scanning?

ASCA performs SAST analysis on source code files like .py, .js, .java, .go, and .ts to find code vulnerabilities. SCA targets dependency manifests and lockfiles such as package.json, requirements.txt, and go.mod to find vulnerable open-source packages.

Can Checkmarx ASCA findings be fixed automatically?

Yes, remediation is performed through the Checkmarx MCP codeRemediation tool, which returns remediation steps applied to the problematic line. Manual or LLM-generated fixes are not permitted; if the MCP is unavailable, the finding is left unfixed.

Why is the Checkmarx MCP tool not available during remediation?

The usual cause is that the cx CLI is not configured or authenticated, so the MCP bridge cannot derive its URL or auth header. Run `cx auth validate` to check, re-run the CLI setup if it fails, and restart the session to reconnect the MCP.

Does the ASCA re-scan fix all findings reported after remediation?

No. The re-scan reads the whole file, so pre-existing findings in untouched code are out of scope and left alone. Only findings tied to the lines you modified are remediated, matched by the problematic line text rather than line number.