sre-init

Files (1)

• SKILL.md

SKILL.md (first lines)

# sre-init repository

**Before any maintainer work:** read `LOCAL.md` at the repo root (local only, gitignored). It contains monorepo paths, release workflow, and what must not appear in public markdown.

## Public layout

| Path | Purpose |
|------|---------|
| `manifest.yaml` | Version, `requires_harness`, bundle → kit lists |
| `kits/` | Production-ready starter kits |
| `skills/` | Agent skills copied to `.claude/skills/` on bundle install |
| `docs/` | Operator's Manual (public) |
| `README.md` | Landing page (embedded on init) |
| `CLAUDE.md` | Short SRE agent orientation (embedded on init) |

## Quality gate

```bash
sentinel sre validate
```

Shipped kits need `README.md` with a compatibility matrix, skill twins for Lua artifacts, and `_test.lua` coverage where applicable.

## Bundles and unbundled kits

- Bundles (`core`, `examples`, `wp-central`, `wp-edge`) are defined under `bundles:` in `manifest.yaml`.
- Kits that live in `kits/` but are deliberately left out of bundles are listed under the top-level `unbundled_kits:` key in `manifest.yaml`.
- When adding a new kit:
  - Decide whether it belongs in a bundle or should be listed in `unbundled_kits:`.
  - Update the table + "Kits in repo, not in a bundle" section in `docs/kits-and-bundles.md`.
  - Keep `manifest.yaml` as the source of truth for both lists (this enables future automated congruence checks between the file and `kits/*/` directories).

## Init behavior

- Minimal `sentinel sre init`: no kits.
- `--with-bundle` / `--starter-kits`: copy kits + skills from this repo (no `.git/`).

Release steps and harness sync: **`LOCAL.md` only.**

From ndx-au/sre-init, MIT.

More from ndx-au/sre-init