receiving-code-review
#6 in Code Quality & AnalysisUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performat…
Overview
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 implementationFrom the project's GitHub description
Our editorial assessment of receiving-code-review is still in review. Facts below come from the repository and our catalogue.
Good for
Technical specifications
Each attribute is labelled with where it came from.
Install
A skill is a set of instructions your agent loads. Install it into the agent you use; there is nothing to host.
$ npx skills add https://github.com/obra/superpowers --skill receiving-code-review- Listing
- skills.shInstall counts come from skills.sh.
Alternatives
Also in Code Quality & Analysis
Same category, not necessarily equivalent.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering.
code-review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match w…
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo.
caveman-review
Compressed code review - one line per finding with location, problem and fix.
Reviews
Community ratings are kept separate from Beav Scout rankings.
No reviews yet. Community reviews and comments are opening soon; you'll be able to rate receiving-code-review once signed in.