Qualflare in Claude Code

Qualflare in Claude Code

The Qualflare plugin for Claude Code brings test coverage into your AI coding sessions. After a one-time /qf-init, you can generate tests for changed files, run your suite and upload results to Qualflare, and fix failures — without leaving the chat. The plugin works with the same 23 frameworks supported by the Qualflare CLI.

The daily workflow

Once setup is done, three slash commands cover the typical cycle:

1. /qf-cover — after writing or editing source files, generates tests for what changed (or --all to cover a whole file/directory), proposing test cases and writing them after your approval.
2. /qf-run — runs your test suite and uploads the results to Qualflare via qf collect.
3. /qf-fix — when tests are red, reads the last run's results and patches your source code until they pass.

An optional end-of-session coverage nudge prints a quiet reminder if you edited source files without touching tests in that session, so gaps don't accumulate silently.

How it differs from the Quo Agent

This plugin operates from inside Claude Code, at the point you're writing code. It's a different surface from the in-app Quo Agent, which analyzes coverage gaps, suggests test cases, and generates test steps from inside the Qualflare web app, rather than generating or fixing code from a chat session.

First-time setup

Run /qf-init once from your project root. It detects your tech stack (languages, frameworks, file counts — across each part of a monorepo), writes a persistent .qualflare/test-state.md context file so future sessions are framework-aware immediately, and adds a Qualflare section to your project's CLAUDE.md.

Full setup and daily workflow guide →

---

See Also

• Qualflare in Claude Code — installation, setup, and daily workflow guide
• Claude Code Plugin Reference — slash commands, hook behavior, and state files
• AI Features — overview of all AI capabilities in Qualflare