Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From cc-harness
Show current harness session status — iteration count, scores, feature progress, and session metrics
npx claudepluginhub jinsong-zhou/cc-harness --plugin cc-harnessHow this command is triggered — by the user, by Claude, or both
Slash command
/cc-harness:harness-statusThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /harness-status — Session Status Display the current state of the harness session. ## Process 1. Check if `SPEC.md` and `harness/` exist. If neither exists, respond: > No active harness session found. Use `/harness <your project description>` to start one. 2. Read these files (skip any that don't exist): - `SPEC.md` — extract the feature list to determine total features and names - `harness/.harness-state.json` — extract iterations, scores, features completed/failed, currentFeature, compactions, startTime - `harness/iteration-log.md` — read the iteration table rows for per...
/harness-statusDisplays harness health from HARNESS.md: last audit, constraints enforcement ratio (deterministic/agent/unverified), garbage collection active ratio, and drift status.
Share bugs, ideas, or general feedback.
Display the current state of the harness session.
Check if SPEC.md and harness/ exist. If neither exists, respond:
No active harness session found. Use
/harness <your project description>to start one.
Read these files (skip any that don't exist):
SPEC.md — extract the feature list to determine total features and namesharness/.harness-state.json — extract iterations, scores, features completed/failed, currentFeature, compactions, startTimeharness/iteration-log.md — read the iteration table rows for per-feature historyharness/qa-feedback.md — extract the latest evaluation result and critical issuesharness/sprint-contract.md — extract current in-progress feature nameCalculate derived metrics:
now - startTime from .harness-state.jsonfeatures.completed / total features from SPEC.mdscores array in .harness-state.jsonDisplay in this format:
## Harness Status
**Project:** [name from SPEC.md H1]
**Duration:** [calculated from startTime]
**Progress:** [completed/total] features complete
**Current:** [currentFeature from state, or sprint-contract feature name, or "None"]
**Avg Score:** [calculated from scores array]
### Iteration Log
[render the contents of harness/iteration-log.md]
### Latest Evaluation
**Feature:** [from qa-feedback.md]
**Result:** [PASS/FAIL from qa-feedback.md]
**Critical Issues:** [list from qa-feedback.md, or "None"]
### Session Metrics
| Metric | Value |
|--------|-------|
| Total iterations | [from state] |
| Features completed | [from state] |
| Features failed | [from state] |
| Compactions | [from state] |
/harness — Start a new session/evaluate — Trigger standalone evaluation