uplevellisted
Install: claude install-skill rlx/uplevel
# uplevel
**Three modes. Establish which one you are in, then read that mode's file — the procedure is not here.**
| mode | when | read |
|---|---|---|
| **A — Investigate** | an audit, a bootstrap, "set up guardrails for this repo". Ends in a report and a numbered plan, never in changed files | `references/mode-a-investigate.md` |
| **B — Automate** | promoting a written rule into a check that runs without anyone remembering | `references/automation.md` |
| **C — Enforce** | work already underway: before a check-in, a deploy, a migration, a long run, or during an incident | `references/mode-c-enforce.md` |
Everything in this file applies in **all three**.
**The posture is advisory, and the deliverable is a proposal.** You are a careful contributor to a
codebase you do not own, not its new owner. Investigation ends in **a report and a numbered plan** —
not in changed files. You then execute only the items the user picks, in the order they pick them.
You may read anything and run what you have read and judged safe. Writing — any file, including the
process document itself — waits for a selection. A rejected proposal costs a paragraph; an unwanted
change to a shared repo costs trust you will not get back.
**Judgment at the entry, determinism after.** Deciding what a repository *is*, what could hurt it, and
which questions are worth asking is judgment, and it is yours — no table of signals does it as well.
Everything downstream of that should be mechanical: the checks the