원클릭으로 Manus에서 모든 스킬 실행

scope-compliance

스타2

포크0

업데이트2026년 6월 27일 09:58

Cross-check a diff against the task packet's allowed/forbidden file lists; enforce R-001 scope boundaries with file:line evidence. Owned by the reviewer.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

mahmoud-emad-dev

mahmoud-emad-dev/aspis

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

scope-compliance

Purpose

Before approving any change, verify every modified file is within the task packet's allowed scope and no forbidden files were touched. A single out-of-scope edit can corrupt the architecture or open a security hole. This is the deterministic half of the scope dimension: scripts check the file list, the reviewer interprets and judges. Reviewer is read-only (R-004) — it verifies, never edits.

When to use

Every change review, before any verdict. Also during plan review: does the plan's stated file list plausibly cover the scope it claims? Run alongside other reviewer skills (constitution-check, evidence-validation).

Procedure

Get the diff file list: git diff --name-only HEAD~1 (or the appropriate base — the last reviewed commit).
Get the allowed file list from the task packet (TASK_PACKET.md / TASKS.md / feature.yaml).
Get the forbidden file list: protected paths per R-008 (.aspis/rules/**, profiles/defaults.yaml, .opencode/agents/**, .claude/agents/**, secrets).
Cross-check: every changed file must be in allowed AND not in forbidden. Report each violation with file:line evidence.
Scope creep (outside allowed, not forbidden): HIGH if it changes architecture or adds capability; MEDIUM if a harmless adjacent cleanup.
Protected-path violation: CRITICAL — requires R-008 human governance approval; reject the change outright.
All files in scope → CLEAN. Any violation → CHANGES-REQUIRED with the violating file:line list as evidence.

Outputs

A scope compliance report:

Changed files list (from git diff --name-only).
Per-file status: ALLOWED | FORBIDDEN | OUT-OF-SCOPE.
Verdict: CLEAN or CHANGES-REQUIRED.
Each finding carries file:line evidence and a severity (CRITICAL / HIGH / MEDIUM).

Anti-patterns

Trusting the builder's claim about which files changed — always run git diff --name-only yourself.
Allowing "quick cleanup" edits that fall outside the allowed list.
Skipping forbidden-path checks because "it's just a documentation file."
Approving a change with scope violations because the rest of the diff looks good.
Confusing scope-control (builder-side discipline) with scope-compliance (reviewer-side verification) — this skill is the reviewer half (R-001).

이 저장소의 다른 Skills

같은 저장소

commit-splitting

mahmoud-emad-dev/aspis

Keep commits atomic — split a mixed change set into scoped, reviewable commits.

2026-07-012

project-onboarding

mahmoud-emad-dev/aspis

The one-time procedure to take an exported project to live — understand it, confirm the name/goal/stack with the user, run the deterministic `aspis bootstrap`, enrich the judgment files (AGENTS.md, ARCHITECTURE, context), verify, and let the package self-clean. Followed by the bootstrap agent.

2026-06-292

architecture-memory

mahmoud-emad-dev/aspis

Keep per-subsystem architectural intent current through the planning loop — read before designing, record an impact report on change, confirm with the user, apply a dated update, and verify the build against approved intent.

2026-06-292

dependency-audit

mahmoud-emad-dev/aspis

Audit a plan's task dependency graph for structural integrity — circular dependencies, missing prerequisites, orphan tasks, and dependency classification (hard/soft/warning). Produces a pass/warn/fail audit report per dependency so planners catch graph errors before build starts.

2026-06-272

clean-tree-precondition

mahmoud-emad-dev/aspis

Every editing agent should start on a clean working tree so parallel work never collides.

2026-06-272

commit-readiness

mahmoud-emad-dev/aspis

Verify hooks ran, no secrets, protected paths untouched, and commit message valid before committing. Owned by the reviewer.

2026-06-272

scope-compliance

Purpose

When to use

Procedure

Get the diff file list: git diff --name-only HEAD~1 (or the appropriate base — the last reviewed commit).

Get the allowed file list from the task packet (TASK_PACKET.md / TASKS.md / feature.yaml).

Get the forbidden file list: protected paths per R-008 (.aspis/rules/**, profiles/defaults.yaml, .opencode/agents/**, .claude/agents/**, secrets).

Cross-check: every changed file must be in allowed AND not in forbidden. Report each violation with file:line evidence.

Scope creep (outside allowed, not forbidden): HIGH if it changes architecture or adds capability; MEDIUM if a harmless adjacent cleanup.

Protected-path violation: CRITICAL — requires R-008 human governance approval; reject the change outright.

All files in scope → CLEAN. Any violation → CHANGES-REQUIRED with the violating file:line list as evidence.

Outputs

A scope compliance report:

Changed files list (from git diff --name-only).

Per-file status: ALLOWED | FORBIDDEN | OUT-OF-SCOPE.

Verdict: CLEAN or CHANGES-REQUIRED.

Each finding carries file:line evidence and a severity (CRITICAL / HIGH / MEDIUM).

Anti-patterns

Trusting the builder's claim about which files changed — always run git diff --name-only yourself.

Allowing "quick cleanup" edits that fall outside the allowed list.

Skipping forbidden-path checks because "it's just a documentation file."

Approving a change with scope violations because the rest of the diff looks good.

Confusing scope-control (builder-side discipline) with scope-compliance (reviewer-side verification) — this skill is the reviewer half (R-001).

name	scope-compliance
description	Cross-check a diff against the task packet's allowed/forbidden file lists; enforce R-001 scope boundaries with file:line evidence. Owned by the reviewer.