Coding Agent Integration
This page explains how to use coding agents such as Codex, Claude Code, and
GitHub Copilot CLI to run inspequte and turn SARIF output into actionable fixes.
Prerequisites
inspequteis installed and available inPATH.- Your repository includes
AGENTS.mdwith project constraints. - You have target inputs ready (
.jar,.class, and classpath paths).
Base workflow
Use the following prompt with your coding agent after running the CLI command.
Read AGENTS.md.
Run:
inspequte --input app.jar --classpath lib/ --output results.sarif
Then:
1) Summarize findings by rule ID.
2) Explain likely root causes.
3) Propose patch-ready fixes with file paths.
Run the analysis in your terminal:
Then ask your agent:
Read AGENTS.md.
Open results.sarif.
1) Summarize findings by rule ID.
2) Explain likely root causes.
3) Propose patch-ready fixes with file paths.
Baseline comparison
Run in your terminal:
inspequte baseline --input app.jar --classpath lib/ --output inspequte.baseline.json
inspequte --input app.jar --classpath lib/ --output results.sarif --baseline inspequte.baseline.json
Then ask your agent:
Repository-wide analysis
Run in your terminal:
Then ask your agent:
Read AGENTS.md.
Open results.sarif.
Group findings by module/package and propose a fix plan in priority order.
Selected-rule analysis
Run in your terminal:
Then ask your agent:
Read AGENTS.md.
Open results.sarif.
Summarize findings only for the selected rule IDs and propose fixes.
rules.txt format for --rules @rules.txt:
- one rule ID per line
- empty lines ignored
- lines starting with # ignored
JSON request mode (--json)
You can pass scan configuration as JSON for stable agent integration:
inspequte --json '{"command":"scan","input":["app.jar"],"classpath":["lib/"],"output":"results.sarif"}'
inspequte --json @request.json
cat request.json | inspequte --json -
--json cannot be combined with:
- --input
- --classpath
- --rules
- --baseline
- --output
- --allow-duplicate-classes
Schema: - https://kengotoda.github.io/inspequte/schemas/cli-option.json
Tips
- Always specify where to write SARIF (
--output). - Ask for summaries that include rule IDs.
- Request patch-ready fixes, not only high-level advice.
- If you automate this in GitHub Actions, see
docs/github-actions.md.