← ClaudeAtlas

readable-codelisted

Make the source a branch changes read plainly, and prove its behaviour unchanged. Use when asked to make this branch readable, for a readability pass, or to simplify or untangle the code a branch changes. Works on the files the branch changes against its target branch, narrowed to the paths passed. Takes a baseline of the full suite, and of the synthesized output where the branch holds infrastructure code, then has the author approve groups of like files and the decisions they share, and launches one task-executor agent per group to apply the team's readability and comment rules with no behaviour change and no rename for taste. Runs both again, asks whether to revert or keep any file whose change made a difference, has the wave-reviewer agent read the pass, sends its blocker and should-fix findings back to the executors to fix, and hands back with the report skill. Not for a test cleanup, which is tighten-tests's; not for a bug, which is bugfix's; not for a new change, which is start-task's. Commits nothing.
sabind/ponderly · ★ 0 · Code & Development · score 69
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