harness-project-calibration

Derives project-specific quality thresholds, high-risk paths, and review blind spots from repository measurements.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-project-calibration-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-project-calibration
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-project-calibration
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-project-calibration-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Global harness defaults ship generic thresholds and path globs that do not match any specific repository, causing quality gates to fail constantly or train teams to ignore review lists. This Skill calibrates those defaults against the project's own measurement history so quality gates reflect reality. ## Core Features & Use Cases - Threshold Derivation: Proposes quality thresholds from the distribution of the project's own baseline runs (minimum, median, latest) rather than copying another project's numbers. - High-Risk Path Mapping: Walks the repository tree to match always-review categories (auth, payments, secrets, migrations, CI workflows) against directories that actually exist, dropping irrelevant globs. - Tool Availability Audit: Lists every unavailable gate metric with the concrete cost of enabling it, so gaps are visible instead of hidden. - Blind-Spot Analysis: Reads escaped-defect logs and bug history to propose review lines describing how this system actually breaks. - Use Case: After running harness-bootstrap on a new repo, run this calibration to produce an approval-gated proposal that updates agent-os/quality-thresholds.json and the Quality section of AGENTS.md with repo-specific values. ## Quick Start Ask the agent to calibrate this project's quality thresholds and high-risk paths from its measurement history and produce an approval-gated proposal.

Frequently Asked Questions about harness-project-calibration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I calibrate quality thresholds for my repository?

Run the calibration procedure, which reads baseline fields in agent-os/quality-thresholds.json, Metrics trailers in git log, and Phase-A reports. It proposes thresholds near the median of recent passing runs and requires operator approval before writing anything.

How are high-risk paths determined for a project?

The skill walks the repository tree and matches always-review categories like auth, payments, secrets, migrations, and CI workflows against directories that actually exist. Categories with no representation are reported, and irrelevant global globs are dropped.

What happens when a quality gate metric is unavailable?

The calibration lists every unavailable metric with the concrete cost of enabling it, such as adding Stryker for mutation testing or a dependency-cruiser config. Gaps are named explicitly so operators can decide what to install.

Does calibration write changes automatically?

No. Output is always an approval-gated proposal; nothing is written before the operator agrees. On approval it writes to agent-os/quality-thresholds.json, appends to quality-decisions.md, and updates the Quality section of AGENTS.md.

When should I not run project calibration?

Do not run it with fewer than three recorded baseline runs, since that is not a valid baseline; stay in Phase A instead. Running twice with no new measurements proposes nothing and reports no new evidence since the last calibration date.