76 pages 75 clean 1 need attention
Page navigation 76

Project

Domains

1

Folders · apps/

Folders · docs/

Folders · knowledge/

Folders · ops/

Folders · packages/

Folders · scripts/

Folders · tests/

Folders · pods/

Folders · tools/

Shared

Metadata clean
Route
/knowledge/portal/project/folders/scripts
Source
knowledge/portal/project/folders/scripts.md
Covered files
0
Last generated
unknown

scripts/

State: folder wiki page generated by deterministic sync

Folder: scripts/

What

scripts/ contains repository automation scripts for sync, guards, and migration tooling. This boundary currently has 6 direct file(s) and 0 direct subfolder(s).

Does

It houses repository automation scripts and helper commands used for repeatable engineering workflows (dominant direct file kinds: .py:4, .md:1, .sh:1).

Why

Automated script boundaries reduce manual drift and keep repeated operations deterministic.

Subfolders

  • (no direct subfolders)

Files

  • README.md — What: scripts/ contains repository automation scripts for sync, guards, and migration tooling. This boundary currently has 6 direct file(s) and 0 direct subfolder(s). Does: It houses repository automation scripts and helper commands used for repeatable engineering workflows (dominant direct file kinds: .py:4, .md:1, .sh:1). Why: Automated script boundaries reduce manual drift and keep repeated operations deterministic.
  • code_doc_guard.py — What: Enforces and can auto-fill What/Does/Why module headers for source files used by wiki maps. Does: Scans registry-covered files, reports header gaps, and optionally writes concise docstring headers for Python modules. Why: Prevents wiki file-map boilerplate and keeps project context cheap for future agents.
  • folder_readme_guard.py — What: Enforce folder README presence/quality for staged or full repo folder sets. Does: Scans folders touched by git changes (or all tracked folders) and validates README.md has non-TODO What/Does/Why fields. Why: Keeps folder ownership context fresh so MAP/wiki navigation stays meaningful as folders are added.
  • install-hooks.sh — What: Source artifact for install hooks in scripts. Does: Contributes implementation or support behavior for this runtime surface. Why: Maintains explicit ownership boundaries for faster agent orientation.
  • secrets_hygiene_gate.py — What: Secrets hygiene gate for CI and promotion workflows. Does: Scans repository files for plaintext secret-like material and validates rotation evidence artifact freshness. Why: Prevents accidental secret commits and blocks promotions without recent key/token rotation evidence.
  • wiki_sync.py — What: Wiki sync module for scripts. Does: Implements WikiPage, _now_iso, _read_text, _iter_repo_files used by this runtime surface. Why: Keeps behavior boundaries explicit so wiki maps stay useful without reading full files.