ericrisco/rsc-harness / skills/harness
harness
FlaggedUse when governing a workspace's control plane, code or not — the `01-TOOLS/` tooling layer, the `02-DOCS/` chaos→knowledge wiki, the root Knowledge map. Audits it, migrates legacy `XX-*` folders, scaffolds provider tooling, sweeps the inbox, eats a file the person hands over ("cómete este fichero", "guárdalo en la documentación": moved into 02-DOCS/raw/ and documented), writes root CLAUDE.md/AGENTS.md. NOT the bootstrap front door (that is `init`, which hands off here).
references/ingest-ignore-defaults.md
View on GitHub# Ignore defaults — what the Auto-Ingest Sweep must never scan
The Auto-Ingest Sweep discovers un-ingested documents across the whole workspace.
`02-DOCS/.rscignore` scopes that scan so it never grabs code, build output, tooling,
the wiki's own internals, or non-document files. This is the single guardrail that
keeps "automatic, workspace-wide" from turning into "tragar lo que no toca".
`02-DOCS/.rscignore` is **tracked** (not gitignored): the team shares the same scan
boundary. Users append their own patterns freely.
## Default `02-DOCS/.rscignore`
```gitignore
# 02-DOCS/.rscignore — paths the Auto-Ingest Sweep must NEVER scan as a knowledge source.
# Tracked (the team shares it). Append your own patterns below.
node_modules/
.git/
.next/
dist/
build/
.venv/
__pycache__/
.dart_tool/
.pytest_cache/
.ruff_cache/
01-TOOLS/
02-DOCS/inbox/_processed/
02-DOCS/raw/
02-DOCS/wiki/
.DS_Store
# Only document-like files are candidates anyway — pdf, docx, doc, md, txt, csv,
# tsv, json, html, rtf, and doc-like images (png/jpg of scans). Everything else
# (code, archives, binaries, lockfiles) is ignored even outside these paths.
```
## App source dirs are ignored at scan time
Beyond the file above, the sweep adds every detected **app source directory** to the
effective ignore set: any directory carrying a manifest (`package.json`,
`pyproject.toml`, `pubspec.yaml`, `go.mod`, `Cargo.toml`) and its tree. Source code is
never a knowledge source — `02-DOCS/wiki/` is where understanding about the code lives,
written deliberately, not scraped from the repo.
## Why `02-DOCS/raw/` and `02-DOCS/wiki/` are ignored
They are *outputs* of ingestion, not inputs. Scanning them would re-ingest the wiki
into itself. `inbox/` is the only `02-DOCS/` subtree the sweep reads as a source
(plus discovered external folders).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |