Using codqual with AI agents
codqual's agent surface is its REST API — there is no client to install. Any coding agent that can run curl (Claude Code, Cursor, Codex, and so on) can read codqual's findings and act on them.
Quickstart
1. Install the skill
One portable SKILL.md works in Claude Code, Cursor, Windsurf, and Codex CLI — download it into your tool's skills directory:
# Claude Code
mkdir -p ~/.claude/skills/codqual && curl -fsSo ~/.claude/skills/codqual/SKILL.md https://codqual.com/SKILL.md
# Cursor
mkdir -p ~/.cursor/skills/codqual && curl -fsSo ~/.cursor/skills/codqual/SKILL.md https://codqual.com/SKILL.md
# Codex CLI
mkdir -p ~/.codex/skills/codqual && curl -fsSo ~/.codex/skills/codqual/SKILL.md https://codqual.com/SKILL.md
# Windsurf
mkdir -p ~/.codeium/windsurf/skills/codqual && curl -fsSo ~/.codeium/windsurf/skills/codqual/SKILL.md https://codqual.com/SKILL.md
2. Create an API key
New accounts get a key at signup (shown once). Create more anytime in the dashboard under Settings → API Keys. The skill checks CODQUAL_API_KEY on first run and walks you through adding it to your shell profile — you never paste the key into the agent chat.
3. First request
Ask your agent something like "fix the open codqual issues in this repo", or verify access directly:
curl -fsS -H "Authorization: Bearer $CODQUAL_API_KEY" "https://api.codqual.com/issues?status=open"
Closing the loop from the PR
After fixing a finding, the agent reports back on the codqual PR comment itself — with the user's own gh auth, never a codqual credential:
- reply /codqual addressed (and react 👍) when the finding was correct and is now fixed;
- reply /codqual dispute <reason> (and react 👎) when it is a false positive — codqual records it as a learning signal for human review, it never silently dismisses;
- suppression stays human: a repo maintainer replies /codqual ignore false-positive (or intentional) to stop a finding from reappearing.
Machine-readable docs
Give your agent https://codqual.com/llms.txt (an index of these docs), https://codqual.com/llms-full.txt (everything in one file), or any page's markdown twin — for example https://codqual.com/docs/api.md.
API contract (OpenAPI)
The three public read endpoints (GET /issues, GET /reviews, GET /reviews/:id) are described by an OpenAPI 3.1 spec at https://api.codqual.com/openapi.json — kept honest by CI against the live route code, same as everything on these pages.