ccc-testing SKILL.md skillA

ccc-testing 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-testing@git:20261025.7eae921

Pins git:20261025.7eae921 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/skills/ccc-testing/SKILL.md
Versions recorded: 5
Latest version: git:20261025.7eae921, committed Oct 25, 2026
First version recorded: Jul 7, 2026
Size: 5,189 bytes
Repository stars: 6
License: MIT

Write or plan tests: TDD, E2E, visual, load, regression, evals and verification, in an isolated worktree. Use to add tests or a test strategy.

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-testing — the right test lane

**CC Commander** · /ccc-testing · one entry to the testing domain; routes to the specialist lane and keeps test work out of your working tree.

## When to use / when not to

- Use when the request is about writing, planning or running tests and the right specialist is not obvious.
- Go straight to `/ccc-qa` for a QA pass over an existing suite, and to `/ccc-e2e` for a parallel pre-release assessment.
- Use `/ccc-systematic-debugging` when a test fails and the cause is unknown.

## What happens

### 1. Match the intent to a lane

An argument or a clear request picks the lane directly:

| Intent | Lane (toolkit sub-skill) | Plugin fallback |
|---|---|---|
| "Write tests first", TDD | `tdd-workflow` | Red-green-refactor inline: write the failing test, run it and show the failure, implement, rerun to green |
| "E2E tests", Playwright | `e2e-testing` + `webapp-testing` | `/ccc-e2e e2e-only` |
| "Verify my work", "is this done?" | `verification-loop`, then `verification-before-completion` | Run the test, lint and build commands the project declares (`package.json` scripts, `Makefile`, `pyproject.toml`) with Bash and quote each exit status |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kevinzai/commander/ccc-testing@sha256:f5d89b592f195960

The line at the top of this page pins the label git:20261025.7eae921, 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_kwrzcitpt3gtlygx.svg)](https://markdownregistry.com/a/art_kwrzcitpt3gtlygx)

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

Versions

The registry has recorded 5 versions of this file, between Jul 7, 2026 and Oct 25, 2026, about one every 28 days.

version	committed	commit	size	audit
git:20261025.7eae921 latest	2026-10-25	7eae921	5,189 B	A	view · diff
git:20261025.3b88727	2026-10-25	3b88727	5,215 B	A	view · diff
git:20261013.fbe187d	2026-10-13	fbe187d	5,354 B	A	view · diff
git:20260801.0de5ac7	2026-08-01	0de5ac7	3,564 B	A	view · diff
git:20260707.947ab2f	2026-07-07	947ab2f	3,430 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 (5189 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_kwrzcitpt3gtlygx
GET https://markdownregistry.com/api/v1/resolve?ref=kevinzai/commander/ccc-testing
GET https://markdownregistry.com/api/v1/blob/f5d89b592f1959601cda23818859570685528b521ec308f4805b3e1059f2e195

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