Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

harness-review

Estrellas0

Forks0

Actualizado25 de marzo de 2026 a las 12:28

Perform a concise, prioritized review of current code changes with concrete fixes, using the repository’s configured review policy and guides.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

Simon-Initiative

Simon-Initiative/harness

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	harness-review
description	Perform a concise, prioritized review of current code changes with concrete fixes, using the repository’s configured review policy and guides.
examples	["$harness-review","Review this diff for risks before I open a PR ($harness-review)"]
when_to_use	["Implementation is complete and needs a quality pass.","The user asks for a review, risk scan, or PR readiness check."]
when_not_to_use	["No meaningful changes are present to review.","The task is pure document drafting with no code or behavior diff."]

Workflow

Inspect the changed files and identify behavior-impacting risks first.
Read harness.yml.
If code review is disabled, stop and report that no repository review gate is configured.
Read docs/CODEREVIEW.md and every repository-local review guide it points to and follow and implement a code review as prescribed, delegating actual review work to the reviewer subagent as outlined in docs/CODEREVIEW.md.
Return findings in severity order.

Output Contract

Findings first.
Then residual risks or test gaps.

Más de este repositorio

mismo repositorio

harness-bootstrap

Simon-Initiative/harness

Seed a target repository with the required harness contract files and directory structure, and optionally draft initial repository-specific content when enough context is available.

2026-03-100

harness-analyze

Simon-Initiative/harness

Convert an informal feature idea into a concise, implementation-ready PRD in a work item directory under docs/exec-plans/current/.

2026-03-100

harness-architect

Simon-Initiative/harness

Transform a PRD into a practical FDD in a work item directory under docs/exec-plans/current/ with concrete boundaries, interfaces, data impacts, and verification strategy.

2026-03-100

harness-design

Simon-Initiative/harness

Produce a slice-level detailed design doc at <work_item_dir>/design/<slice_slug>.md by mapping slice responsibilities, interfaces, edge cases, and tests to the work item requirements.

2026-03-100

harness-develop

Simon-Initiative/harness

Implement one phase from a work item plan under docs/exec-plans/current/ using the repository contract as the source of truth.

2026-03-100

harness-plan

Simon-Initiative/harness

Convert PRD and FDD into a dependency-ordered implementation plan in a work item directory under docs/exec-plans/current/ with explicit gates and verification notes.

2026-03-100

name	harness-review
description	Perform a concise, prioritized review of current code changes with concrete fixes, using the repository’s configured review policy and guides.
examples	["$harness-review","Review this diff for risks before I open a PR ($harness-review)"]
when_to_use	["Implementation is complete and needs a quality pass.","The user asks for a review, risk scan, or PR readiness check."]
when_not_to_use	["No meaningful changes are present to review.","The task is pure document drafting with no code or behavior diff."]

Workflow

Inspect the changed files and identify behavior-impacting risks first.
Read harness.yml.
If code review is disabled, stop and report that no repository review gate is configured.
Read docs/CODEREVIEW.md and every repository-local review guide it points to and follow and implement a code review as prescribed, delegating actual review work to the reviewer subagent as outlined in docs/CODEREVIEW.md.
Return findings in severity order.

Output Contract

Findings first.
Then residual risks or test gaps.