ccc-qa SKILL.md skillA

ccc-qa from kevinzai/commander is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add kevinzai/commander/ccc-qa@git:20261013.fbe187d

Pins git:20261013.fbe187d in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: kevinzai/commander
Path: commander/cowork-plugin-codex/skills/ccc-qa/SKILL.md
Versions recorded: 5
Latest version: git:20261013.fbe187d, committed Oct 13, 2026
First version recorded: May 8, 2026
Size: 9,183 bytes
Repository stars: 6
License: MIT

QA pass before shipping: detects the framework, runs unit, integration and E2E suites, computes the coverage delta, audits flaky tests and has qa-engineer severity-rate gaps. Use when the user asks for a QA pass, to run all tests, check coverage, find flaky tests or if it is ready to ship.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# $ccc-qa — QA pass before you ship

**CC Commander** · $ccc-qa · every suite run, coverage delta, flaky tests and missing edge cases, severity-rated.

## When to use / when not to

- Use for "QA pass", "run all tests", "check coverage", "find missing tests", "flaky test", "is this ready to ship", or when `$ccc-review` or `$ccc-ship` hands off here.
- Use `$ccc-testing` first when the project has no tests yet; it scaffolds a suite.
- Skip it for a single-function fix (write the targeted unit test directly) and for docs- or config-only changes with no testable behavior.
- Use `$ccc-e2e` for a fanned-out pre-release assessment across isolated worktrees.

## What happens

### 1. Detect the framework

Run in parallel with Bash; a failing probe means "not this framework":

```bash
grep -E '"(vitest|jest|@playwright/test|mocha|cypress|jasmine)"' package.json 2>/dev/null | head -10
ls vitest.config.* jest.config.* playwright.config.* pytest.ini setup.cfg pyproject.toml go.mod Cargo.toml pom.xml 2>/dev/null
python3 -m pytest --collect-only -q 2>/dev/null | tail -3
cat .ccc/coverage-history.json 2>/dev/null
```

| Evidence | Framework | Run command |
|---|---|---|
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kevinzai/commander/ccc-qa@sha256:556aa3377e75d96f

The line at the top of this page pins the label git:20261013.fbe187d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_ms2mqfvk5dgzr5a4.svg)](https://markdownregistry.com/a/art_ms2mqfvk5dgzr5a4)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between May 8, 2026 and Oct 13, 2026, about one every 40 days.

version	committed	commit	size	audit
git:20261013.fbe187d latest	2026-10-13	fbe187d	9,183 B	A	view · diff
git:20260722.9d3ab82	2026-07-22	9d3ab82	8,823 B	A	view · diff
git:20260707.947ab2f	2026-07-07	947ab2f	8,691 B	A	view · diff
git:20260514.2648602	2026-05-14	2648602	8,522 B	A	view · diff
git:20260508.d1f6704	2026-05-08	d1f6704	8,538 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (9183 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

kevinzai/commander · 6 stars · license MIT · pushed 2026-11-08 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ms2mqfvk5dgzr5a4
GET https://markdownregistry.com/api/v1/resolve?ref=kevinzai/commander/ccc-qa
GET https://markdownregistry.com/api/v1/blob/556aa3377e75d96f5de7db3dfeaff0213843739fca1afae88b5fbf74ea6bd65b

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from kevinzai/commander

mintlify SKILL.md skill

kevinzai/commander · .agents/skills/mintlify/SKILL.md · Build and maintain documentation sites with Mintlify. Use when

v1.0 · audit A · 6 stars

.cursorrules Cursor rule

kevinzai/commander · .cursorrules

git:20260327.b10b207 · audit A · 6 stars

AGENTS.md AGENTS.md file

kevinzai/commander · AGENTS.md