Orchestrates iterative review, fix, and verification loops on code diffs before PR handoff.
npx skills add https://github.com/sandsower/beislid --skill rinse-sandsower
Please help me install this Agent Skill. Skill: rinse Source: https://github.com/sandsower/beislid/tree/main/skills/rinse Command: npx skills add https://github.com/sandsower/beislid --skill rinse-sandsower
review primitive after each fix round, comparing new findings against previous ones. - Stop and escalation conditions: Detects when repeated blocking findings in the same subsystem signal a design flaw and routes the work to redesign instead of more patching. - Use Case: Before handing off a feature branch for PR review, run the loop to triage findings, apply approved fixes, run tests, and repeat until no Critical or Important issues remain. ## Quick Start Run a rinse loop on my current branch against main, fixing only Critical and Important findings with my approval before each change.High-intent search queries and answers about installing and using this skill.
Invoke the rinse loop with a diff range such as a merge-base against main. It runs the review primitive, triages findings by severity with you, applies only approved fixes, runs verification, and reruns review until no blocking findings remain.
A single review pass is side-effect-free and only reports findings. Rinse is an orchestrator that edits files, runs verification, and repeats review passes within user-approved boundaries until the branch converges.
Yes. Before any edits, rinse asks you to set a fix boundary: Critical only, Critical plus Important, all findings, or a custom file/path scope. It obeys that boundary for the whole loop unless you explicitly change it.
Stop when the same subsystem produces blocking findings for two consecutive iterations, a fix introduces new blocking findings elsewhere, or verification failures point to unclear requirements. Rinse then escalates to a blueprint/redesign step rather than more patching.
Yes. After applying approved fixes, it runs verification appropriate to the changed files, preferring configured project gates or inferred checks like unit tests, typecheck, build, and lint. Failed verification is investigated before further code changes.
gitkrakenRestructures a feature branch's commits into a minimal, reviewable history with a byte-identical final tree.
lachlanchenRebase a GitHub pull request onto main, apply review fixes, run tests, and push.
jpoleyValidate security patch quality and regression risk for code changes.
AndurilCodeDeconstruct assumptions and rebuild solutions from fundamental truths.