Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

harness-review

Étoiles106

Forks9

Mis à jour14 juin 2026 à 09:42

Review the current change set from an opposing harness-engineering perspective. Use when the user asks for /harness review, /harness review sub-agent, or a no-edit harness review.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

harnessworks

harnessworks/harness-starter-kit

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	harness-review
description	Review the current change set from an opposing harness-engineering perspective. Use when the user asks for /harness review, /harness review sub-agent, or a no-edit harness review.
argument-hint	[sub-agent] [focus]

Harness Review

Challenge the current change set before completion.

Steps

Read ../../references/package-contract.md.
Read ../../references/review-workflow.md.
If ./harness-starter-kit/commands/harness-review.md exists in the target, prefer that canonical workflow.
Inspect the current diff and relevant harness guidance.
If the request includes sub-agent, use a read-only reviewer subagent only when the active runtime permits it. Otherwise fall back and report why.
Lead with findings by severity. If there are no actionable findings, say so clearly and name residual test gaps or risks.

Boundaries

Do not modify files unless the user explicitly asks to apply fixes after the review.
Prioritize bugs, source-of-truth risks, overreach, missing checks, stale docs, and durable-memory gaps.

Plus depuis ce dépôt

même dépôt

harness-adopt

harnessworks/harness-starter-kit

Apply Harness Starter Kit prompt-first adoption to a target repository. Use when the user asks to apply, install, adopt, or bootstrap repository harness guidance, checks, memory, and adoption reporting.

2026-06-14106

harness-doctor

harnessworks/harness-starter-kit

Run the diagnostic Harness Doctor workflow. Use when the user asks for /harness doctor, harness score, repository harness readiness, or a no-edit harness health report.

2026-06-14106

harness-refresh

harnessworks/harness-starter-kit

Review stale, duplicated, obsolete, or unused target harness guidance. Use when the user asks for /harness refresh or wants harness maintenance recommendations without default edits.

2026-06-14106

harness

harnessworks/harness-starter-kit

Route Harness Starter Kit workflows. Use when the user invokes /harness with adopt, doctor, update, refresh, review, or review sub-agent, or asks to apply, diagnose, maintain, or review repository harness guidance.

2026-06-14106

harness-update

harnessworks/harness-starter-kit

Refresh an adopted target repository from the latest Harness Starter Kit reference. Use when the user asks for /harness update or wants source tracking and selective harness updates.

2026-06-14106

name	harness-review
description	Review the current change set from an opposing harness-engineering perspective. Use when the user asks for /harness review, /harness review sub-agent, or a no-edit harness review.
argument-hint	[sub-agent] [focus]

Harness Review

Challenge the current change set before completion.

Steps

Read ../../references/package-contract.md.
Read ../../references/review-workflow.md.
If ./harness-starter-kit/commands/harness-review.md exists in the target, prefer that canonical workflow.
Inspect the current diff and relevant harness guidance.
If the request includes sub-agent, use a read-only reviewer subagent only when the active runtime permits it. Otherwise fall back and report why.
Lead with findings by severity. If there are no actionable findings, say so clearly and name residual test gaps or risks.

Boundaries

Do not modify files unless the user explicitly asks to apply fixes after the review.
Prioritize bugs, source-of-truth risks, overreach, missing checks, stale docs, and durable-memory gaps.