Skip to content
rd-skills
All skills

filesystem-process-safety

FoundationJIT only

Use when code mutates files, resolves paths, applies file protection, or controls child processes. Skip uploads, shell syntax, build graphs, services, and host administration.

Group
Cross-cutting safety
Supported roles
MainAnalysisTaskReview
Source
SKILL.md

Use when

Trigger signals that make this skill the right owner

  • local file mutation path resolution file protection writer trust classification or direct child-process control changes application behavior

Do not use when

Anti-triggers — as binding as the triggers above

  • uploads shell-language semantics build graphs service rules or host administration
  • no local filesystem mutation path-authority writer-trust or child-process contract changes
  • a path or mutability is mentioned but no filesystem behavior or direct child-process behavior changes

Required inputs

What must be supplied before this skill can decide anything

  • current task contract
  • selected primary Professional Skill
  • task-local trigger evidence

Output contract

What this skill owes the next role

  • Return a normal Filesystem/Process Safety Record covering create or replace, atomicity, durability, legitimate concurrency, cleanup, wait and reap, stdout/stderr, timeout or cancellation, and result reconciliation.
  • Add trust-sensitive protection only when its Reference loads, with separate actor or writer, privilege or sensitive asset, and reachable material impact decisions.

Escalation signals

When this skill must hand the decision back

  • path authority writer identity writer trust mutation scope process identity completion certainty cleanup or recovery remains materially unresolved

Loaded by

This skill never owns a task. These professionals may pull it in as Layer 3.

Targeted references

Each reference carries its own load condition. None of them enter context by default.

ReferenceLoad whenDo not load whenRequired by
atomic-filesystem-commit-and-containment.mdtargetedLocal creation, replacement, durability, containment, link, permission, ownership, or cleanup semantics remain openNo local filesystem mutation or path-authority decision changesAnalysisTaskReview
child-process-invocation-and-completion.mdtargetedExecutable selection, argv, environment, stdio, exit, timeout, cancellation, descendants, or result certainty remains openNo direct child-process execution contract changesAnalysisTaskReview
trust-sensitive-filesystem-process-protection.mdtargetedA current filesystem or direct child-process effect has concrete reachable trust evidence, or a complete related Core critical unknown remainsOnly normal filesystem or process correctness applies, or trust evidence is generic, disconnected from the current effect, or unreachableAnalysisTaskReview