Qf Fix (Grade A)Tegemist salvestamine ja kooditöötel jaudu

When something's off?

Run /qf-doctor first. It checks the things that break most often: Is qf installed and available on your PATH? Is each package's identifier configured locally (qf projects lists them)? Is your test-state.md still current, or has the project drifted since setup? Do the framework slugs in the plugin match the installed CLI? Most issues are a missing CLI or a missing qf login. Fix what the doctor flags and re-run.

Asked by Pierre Dubois · Sep 10, 2025

What you can do?

Every command runs from the Claude Code chat — no terminal, no config files. | Command | When to use it | |---------|----------------| | /qf-init | Once, to set up a new project — detects frameworks, counts test files, and optionally enables the coverage nudge | | /qf-cover [path or glob] | After writing code — generates tests for the source files you just changed | | /qf-run [slug or results-file] | When you're ready to verify — runs your test suite and uploads results to Qualflare | | /qf-fix [slug or path] | When tests are red — analyzes the last run and patches your code until they pass | | /qf-doctor | When something feels wrong — health check covering CLI, auth, config, slug drift, and file-count drift | | /qf-update [slug or path] | When you've added test files — refreshes counts without re-running full setup | | /qf-state | When you want to see what Qualflare knows — shows frameworks, file counts, and hook status | | /qf-hook on\|off | Any time — toggle the end-of-session coverage nudge on or off |

Asked by Gideon Mwangi · Aug 26, 2025

How it stores state?

/qf-init creates a .qualflare/ directory in your project root: Add .qualflare/results/ to your .gitignore. The other two files are meant to be committed — they give every session the context it needs without running setup again.

Asked by Quang Nguyen · Jul 14, 2025