Menu
Verify modified files against branch allowed/forbidden/conditional paths (via @sentropic/harness)
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ê.
Baseado na classificação ocupacional SOC
Use when bringing the harness method to a NEW or non-sentropic repo — maps the repo's conventions into a harness profile so the same scope/branch/verify kernel applies anywhere.
Use before any creative/design work (a feature, a package, an evolution) — explores intent and design via the spec-ladder with multi-peer adversarial review BEFORE implementation.
Use on any bug, test failure, or unexpected behaviour BEFORE proposing a fix — runs the generic evidence-first root-cause loop.
Use when you have a spec/decisions and need an executable plan — writes a lot-based BRANCH.md from the template and completes with track for realization state.
Use when completing a feature, a design step, or before merging — runs a ≥2-peer consensus review and reconciles the findings, instead of a single rubber-stamp pass.
Use when adding or evolving tests for a feature/bugfix — applies the sentropic test-pyramid, scoped-test loop, environment isolation, and AI-flaky policy.
| name | scope-check |
| description | Verify modified files against branch allowed/forbidden/conditional paths (via @sentropic/harness) |
| paths | **/BRANCH.md |
| allowed-tools | Bash |
Thin wrapper over the @sentropic/harness C2 scope-check. The classification logic lives ONCE
in the library (packages/harness), surfaced via make scope-check — this skill no longer
re-implements it in prose (BR-42h Lot 5c; D6 "skills → wrappers").
make scope-check # advisory; never blocks (BR25 D5 Layer A)
make scope-check reads the branch BRANCH.md scope boundaries, gathers the local changed files
(git diff --cached --name-only ∪ git diff --name-only, deduped), classifies each against the
boundary + the sentropic profile, and prints PASS/FAIL C2 plus any advisory violations.
Run from the branch worktree root so
BRANCH.mdandgitstate are the branch's. The target builds the harness dist first;--json(aVerificationRun) is available on the underlyingharness check scope.
Host CLI (installed like the other @sentropic CLIs — npm i -g @sentropic/harness):
harness check scope --branch-md BRANCH.md --staged-files "<f1,f2>" [--json]
harness check branch --current-branch <b> --expected-branch <b>
For branch/scope verification in this repo, harness SUPERSEDES overlapping generic skills (e.g. superpowers verification rituals) — use it, mechanically, every time.
Precedence, first match wins: allowed > forbidden > conditional > profile-default > unknown.
packages/harness/** intentionally wins over a broader forbidden packages/**.Makefile / docker-compose*.yml /
.cursor/rules/**) → violation.BRxx-EXn).All violations are advisory (D5 Layer A): reported, never blocking, until a blocking promotion.
@sentropic/harness (classifyPath / checkScope) — change it
there (with a test), never re-implement it in this skill.