Codex Integration

This page explains how to use Codex to run inspequte and turn SARIF output into actionable fixes.

Prerequisites

• inspequte is installed and available in PATH.
• Your repository includes AGENTS.md with project constraints.
• You have target inputs ready (.jar, .class, and classpath paths).

Basic prompt

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.

Prompt with baseline

Create baseline:
inspequte baseline --input app.jar --classpath lib/ --output inspequte.baseline.json

Run comparison:
inspequte --input app.jar --classpath lib/ --output results.sarif --baseline inspequte.baseline.json

Then report only newly introduced findings and propose fixes.

Prompt for repository-wide analysis

Run:
inspequte --input @inputs.txt --classpath @classpath.txt --output results.sarif

Then group findings by module/package and propose a fix plan in priority order.

Tips

• Always tell Codex where to write SARIF (--output).
• Ask Codex to include rule IDs in summaries.
• Request patch-ready fixes, not only high-level advice.
• If you automate this in GitHub Actions, see docs/github-actions.md.