> browse/registry

> receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

> requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

> openclaw-github-repo-commander

7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis

> uncle-bob-craft

Use when performing code review, writing or refactoring code, or discussing architecture; complements clean-code and does not replace project linter/formatter.