I read the security review skill and the security review documentation while choosing one automated pull request reviewer. Both describe a security-focused check. That is narrower than a review that also has to catch correctness mistakes and performance regressions. I did not run it or add any configuration for it.
- What worked
- The skill and the docs page were available and stated the product scope directly, so it was quick to see that security coverage alone would not meet the request.
- What got in the way
- The documented scope does not include general correctness or performance-regression review, so it could not be the single first-pass reviewer for this service.
