Skip to content
Skills Library
AI & agents · Building & coding

chroot

/chroot

Use to create a tighter file-access jail than /scope — explicit file list, not glob patterns. Useful for "I only want AI touching these 12 specific files". Backed by src/services/chroot.ts.

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 create a tighter file-access jail than /scope — explicit file list, not glob patterns. Useful for "I only want AI touching these 12 specific files". Backed by src/services/chroot.ts.

Triggers from the description

I only want AI touching these 12 specific files
Original author description

Use to create a tighter file-access jail than /scope — explicit file list, not glob patterns. Useful for "I only want AI touching these 12 specific files". Backed by src/services/chroot.ts.

How it works

  1. When chroot beats scope
  2. Method (set)
  3. Method (check)
  4. Method (release)
  5. Output shape
  6. Rules
  7. Anti-patterns
  8. When NOT to use
  9. Subagent dispatch
  10. Value over native CC + scope
Original SKILL.md headings · 71 lines, 293 words
SKILL.md preview
---
name: chroot
description: Use to create a tighter file-access jail than /scope — explicit file list, not glob patterns. Useful for "I only want AI touching these 12 specific files". Backed by src/services/chroot.ts.
---

# chroot

Tight jail. Explicit file list, not glob. Stricter than `/scope`.

## When chroot beats scope

- `/scope` — pattern-based; flexible; "all of src/auth"
- `/chroot` — file-list-based; rigid; "exactly these 12 files"

Chroot for: deep refactors where you want to forbid surprise edits anywhere else.

## Method (set)

1. **Patterns.** User specifies glob patterns (e.g. `src/auth/**/*.ts`, `!src/auth/secrets/**`).
2. **Expand** via `src/services/chroot.ts` `ChrootManager.setChroot`. Negation patterns (`!`) excluded.
3. **Persist** the **explicit file list** (not the patterns) — pinned at jail-set time.
4. **Confirm.** Show file count + first 10 files.

## Method (check)

`ChrootManager.checkFile(path)` returns true/false. Used by tooling to enforce.

## Method (release)

`ChrootManager.clearChroot()` removes `.siftcoder/chroot.json`. Confirm with user.

## Output shape

```
Setting chroot:
  Patterns: ["src/auth/**/*.ts", "!src/auth/secrets/**"]

Expanded:    14 files
Sample:
  - src/auth/middleware.ts
  - src/auth/session.ts
  - src/auth/jwt.ts
  - ... (11 more)

Status: jail active
```

## Rules

- **List pinned at set-time.** Adding files to disk after chroot doesn't auto-include them.
- **Negation patterns first.** `["src/auth/**", "!src/auth/secrets/**"]` is explicit.
- **Single-jail per project.** Don't try to layer multiple chroots.
- **Backup on release.** Save the list to checkpoints so it's recoverable.

## Anti-patterns

- Setting chroot then expecting new files to be auto-included (they aren't)
- Combining chroot with scope (use one)
- Chroot too narrow (blocks the task itself)
- Forgetting to release after task complete

## When NOT to use

- Pattern-shaped boundary works — `/scope`
- Greenfield — no jail needed yet
- Multi-developer mob session — chroot is per-project, can collide

## Subagent dispatch

- None — `ChrootManager` is direct

## Value over native CC + scope

Scope is patterns — flexible. Chroot is explicit file list — rigid. The rigidity IS the value when you genuinely want to lock a refactor to a known set.

Versions

The database has no other skills named chroot.

Database snapshot: 13.11.2026 · package version 24bd8eb4caa4 (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

  • 100steering-matcher
    Match file paths against steering file glob patterns to determine applicable steering guidance. Use when you say "match steering for these files", "which steering applies to this task", or "inject steering context". Use when orchestrator needs to inject context-aware guidance…
  • 95creating-claude-rules
    Use when creating or fixing .claude/rules/ files - provides correct paths frontmatter (not globs), glob patterns, and avoids Cursor-specific fields like alwaysApply

Feedback and reports

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