Skip to content
Skills Library
Programming · Automation

scope

/scope

Use to define/show/modify the .siftcoder/scope.json file that the boundary-enforcer hook reads. Bounds where AI can write. "Limit to these files", "lock down scope", "show current scope".

Repository
sift-coder ↗
Licence
MIT
Last repository change
03.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 03.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use to define/show/modify the .siftcoder/scope.json file that the boundary-enforcer hook reads. Bounds where AI can write. "Limit to these files", "lock down scope", "show current scope".

Triggers from the description

Limit to these fileslock down scopeshow current scope
Original author description

Use to define/show/modify the .siftcoder/scope.json file that the boundary-enforcer hook reads. Bounds where AI can write. "Limit to these files", "lock down scope", "show current scope".

How it works

  1. Schema
  2. Method (set)
  3. Method (show)
  4. Method (clear)
  5. Method (add / remove)
  6. Output shape
  7. Rules
  8. Anti-patterns
  9. When NOT to use
  10. Subagent dispatch
Original SKILL.md headings · 83 lines, 318 words
SKILL.md preview
---
name: scope
description: Use to define/show/modify the .siftcoder/scope.json file that the boundary-enforcer hook reads. Bounds where AI can write. "Limit to these files", "lock down scope", "show current scope".
---

# scope

Manage `.siftcoder/scope.json` — the allow/deny list the `boundary-enforcer.mjs` hook enforces.

## Schema

```json
{
  "allow": ["src/auth/**", "tests/auth/**"],
  "deny":  ["src/auth/secrets/**"]
}
```

- **No scope file** → all writes allowed (only blocked by Claude Code's own permissions)
- **Scope set** → writes only to `allow` patterns; `deny` always wins over `allow`

## Method (set)

1. **Patterns.** User specifies allow + (optional) deny.
2. **Validate.** Each pattern must be syntactically valid; warn on patterns that match nothing.
3. **Persist** via `src/services/state.ts` `StateManager.saveScope`.
4. **Confirm.** Show what's currently in scope.

## Method (show)

1. Load scope.
2. Render allow + deny patterns.
3. Optionally expand patterns to file count.

## Method (clear)

1. Confirm with user (clearing scope removes all bounds).
2. Delete `.siftcoder/scope.json`.

## Method (add / remove)

Mutate the file via `StateManager`.

## Output shape

```
Current scope (.siftcoder/scope.json):
  Allow:
    - src/auth/**
    - tests/auth/**
  Deny:
    - src/auth/secrets/**

Effective files:    142 allowed, 3 denied

Hook status:        boundary-enforcer.mjs active in PreToolUse Write|Edit
```

## Rules

- **Deny wins over allow.** A path matching both is denied.
- **Pattern syntax is glob.** `**` for recursive, `*.ext` for extension.
- **Validate before save.** Warn if a pattern matches nothing (likely typo).
- **Backup on clear.** Save the cleared scope to `.siftcoder/checkpoints/scope-cleared-<ts>.json` so it can be recovered.

## Anti-patterns

- Allow `**` (defeats the point of scope)
- Forgetting to set deny for secrets
- Setting overly narrow scope that blocks legit work
- Ignoring "matches nothing" warnings

## When NOT to use

- Greenfield (no scope needed yet)
- Single-file edit (use Claude Code's own `--allowed-file` if available)
- Pre-merge review (different concern)

## Subagent dispatch

- None — uses `StateManager` directly
- Optional: `Explore` to validate patterns by listing matches

## Value over native CC

CC has its own permission system but doesn't natively support per-project allow/deny scope files enforced via hook. Scope IS the value — explicit project-scoped boundaries.

Versions

RepositoryScoreLicence
This page · ialameh/sift-coder100MIT
crisandrews/clawcode100MIT
camoa/claude-skills100MIT
alexzio00/sovereign-skills100MIT
nirkaufman/claude-code-workshop-assets100MIT
ccplugins/awesome-claude-code-plugins100Apache-2.0
lilly-logic-labs/lll-skills90MIT
technicalpickles/pickled-claude-plugins90MIT
suboss87/FDEOps90MIT

Database snapshot: 13.11.2026 · package version d76b7a6f5a9a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100test-naming-enforcer
    Test Naming Enforcer - Auto-activating skill for Test Automation. Triggers on: test naming enforcer, test naming enforcer Part of the Test Automation skill category. Use when writing or running tests. Trigger with phrases like "test naming enforcer", "test enforcer", "test".
  • 90siftcoder
    Use as a meta-skill — "which SiftCoder skill should I use for X". Decision tree across families. Use when user is unsure which specific skill applies.
  • 90matlab-configure-scope-object
    Prevents crashes due to problematic scope-related API misuse caused by agent escalation into internal scope framework objects. Use when configuring properties of scope-related Simulink blocks or MATLAB objects — constrains the agent to documented APIs and directs users to the…
  • 100scope-statement-drafting
    Use this skill when a team must define what its management system covers before a certification project, or its current scope is one vague sentence, and asks "write our ISMS scope", "what should be in scope", "can we exclude the sales office", "scope for the certificate", "draw…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.