Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

harness-review

Estrelas0

Forks0

Atualizado25 de março de 2026 às 12:28

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

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

Simon-Initiative

Simon-Initiative/harness

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·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.

Mais deste repositório

mesmo repositório

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.