readable-codelisted
Install: claude install-skill sabind/ponderly
# Make a branch readable
Run a readability pass over the source a branch changes: one executor per group of like files, all following one list of shared decisions, applies the "Write for the reader." bullet of the `code-changes` rule and the `comments` rule to them, then the full suite, and the synthesized output where there is infrastructure code, prove that nothing behaves differently, and the reviewer reads the pass. The pass changes how the code reads, never what it does.
The author is accountable for the code. A difference from the Baseline is the author's to judge: name the file and ask, never decide it alone. Commit nothing, and change no file yourself beyond restoring one the author chose to revert.
Paths to narrow the pass to, if the author gave any: $ARGUMENTS
Terms used below:
- The **Scope** is the files the branch changes against its target branch, uncommitted and untracked work included, narrowed to the paths passed when there are any.
- A **source file** is a file in Scope that holds code the project runs or deploys. Tests, documentation, configuration, lock files and generated files are not source files; a test cleanup is `tighten-tests`'s.
- **Infrastructure code** is infrastructure-as-code that generates deployment templates. Its **synthesized output** is the templates the project's command that generates them produces.
- The **Run_Folder** is the folder step 2 makes in the session's scratchpad for this run's own records: the Baseline copies and the syn