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

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

Commencer

scope-check

Étoiles1

Forks0

Mis à jour8 juin 2026 à 15:03

Verify modified files against branch allowed/forbidden/conditional paths (via @sentropic/harness)

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

rhanka

rhanka/sentropic

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

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	scope-check
description	Verify modified files against branch allowed/forbidden/conditional paths (via @sentropic/harness)
paths	**/BRANCH.md
allowed-tools	Bash

Scope Check

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").

Run

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.md and git state are the branch's. The target builds the harness dist first; --json (a VerificationRun) is available on the underlying harness 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.

Classification (canonical — owned by the library)

Precedence, first match wins: allowed > forbidden > conditional > profile-default > unknown.

allowed → OK. Allowed is the granted implementation scope: an explicitly-allowed subtree such as packages/harness/** intentionally wins over a broader forbidden packages/**.
forbidden (explicit, or a profile default such as Makefile / docker-compose*.yml / .cursor/rules/**) → violation.
conditional → violation unless a declared exception id matches the profile grammar (BRxx-EXn).
unknown (outside Allowed/Forbidden/Conditional) → advisory violation — intentionally stricter than the old "warning", to surface undeclared scope drift.

All violations are advisory (D5 Layer A): reported, never blocking, until a blocking promotion.

Rules

Checks both staged and unstaged local changes.
Run before every commit to catch scope drift early.
The classification is owned by @sentropic/harness (classifyPath / checkScope) — change it there (with a test), never re-implement it in this skill.

Plus depuis ce dépôt

même dépôt

adopt

rhanka/sentropic

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.

2026-06-101

brainstorm

rhanka/sentropic

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.

2026-06-101

debug

rhanka/sentropic

Use on any bug, test failure, or unexpected behaviour BEFORE proposing a fix — runs the generic evidence-first root-cause loop.

2026-06-101

plan

rhanka/sentropic

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.

2026-06-101

review

rhanka/sentropic

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.

2026-06-101

test

rhanka/sentropic

Use when adding or evolving tests for a feature/bugfix — applies the sentropic test-pyramid, scoped-test loop, environment isolation, and AI-flaky policy.

2026-06-101

Scope Check

Run

make scope-check # advisory; never blocks (BR25 D5 Layer A)

Run from the branch worktree root so BRANCH.md and git state are the branch's. The target builds the harness dist first; --json (a VerificationRun) is available on the underlying harness 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.

Classification (canonical — owned by the library)

Precedence, first match wins: allowed > forbidden > conditional > profile-default > unknown.

allowed → OK. Allowed is the granted implementation scope: an explicitly-allowed subtree such as packages/harness/** intentionally wins over a broader forbidden packages/**.

forbidden (explicit, or a profile default such as Makefile / docker-compose*.yml / .cursor/rules/**) → violation.

conditional → violation unless a declared exception id matches the profile grammar (BRxx-EXn).

unknown (outside Allowed/Forbidden/Conditional) → advisory violation — intentionally stricter than the old "warning", to surface undeclared scope drift.

All violations are advisory (D5 Layer A): reported, never blocking, until a blocking promotion.

Rules

Checks both staged and unstaged local changes.

Run before every commit to catch scope drift early.

The classification is owned by @sentropic/harness (classifyPath / checkScope) — change it there (with a test), never re-implement it in this skill.