Secure Error Handling (harperaa) vs Security Review (waybarrios)
Secure Error Handling (harperaa) and Security Review (waybarrios) are both Security skills, so an agent choosing between them is matching on descriptions that overlap. Here is where they actually diverge.
Secure Error Handling
harperaa
A secure-coding pattern for the error path: return generic, environment-aware messages to users while logging the detail server-side, so a stack trace, database error, or file path never hands an attacker a map of your system. It shapes how failures are surfaced — not a scanner that finds the leaks for you, and narrower than a full security review: it does not cover auth, input validation, or the other vulnerability classes, only how errors are reported.
1 scenario in the bank answer to it
Security Review
waybarrios/opencode-power-pack
Inspects the unmerged commits on a branch and calls out concrete security problems that show realistic exploitation paths, so reviewers can decide whether changes are safe to merge. Unlike broader security-audit or SAST-style tools, it intentionally skips stylistic, architecture, dependency-wide, or general code-review concerns and concentrates only on high-confidence, actionable vulnerabilities in the pending diff.
2 scenarios in the bank answer to it
What is the difference between Secure Error Handling (harperaa) and Security Review (waybarrios)?
- Secure Error Handling (harperaa)
- A secure-coding pattern for the error path: return generic, environment-aware messages to users while logging the detail server-side, so a stack trace, database error, or file path never hands an attacker a map of your system. It shapes how failures are surfaced — not a scanner that finds the leaks for you, and narrower than a full security review: it does not cover auth, input validation, or the other vulnerability classes, only how errors are reported.
- Security Review (waybarrios)
- Inspects the unmerged commits on a branch and calls out concrete security problems that show realistic exploitation paths, so reviewers can decide whether changes are safe to merge. Unlike broader security-audit or SAST-style tools, it intentionally skips stylistic, architecture, dependency-wide, or general code-review concerns and concentrates only on high-confidence, actionable vulnerabilities in the pending diff.
Should I use Secure Error Handling or Security Review (waybarrios)?
The clearest answer is a situation each one is unambiguously right for. Both of these are drawn from the game's question bank.
Reach for Secure Error Handling when
After last Tuesday's PostgreSQL meltdown, the company's public 500 page leaked the live connection string and internal locations to every visitor, so the CTO demanded a coding convention that shows zero implementation detail to browsers while keeping all diagnostics in a backend log.
The skill shapes the visible side of failures by framing a coding convention: it tells you to give browsers a bland, context-aware notice and to sequester every technical artifact—live connection strings, internal locations, diagnostic output—inside server logs, which exactly resolves the split the CTO asked for. semgrep-rule-creator-trailofbits is the genuinely tempting distractor because the leak feels like a source-level artifact you could catch with a static-analysis rule, but that skill merely writes reusable Semgrep detection rules for specific bug patterns and paired test cases; it never influences what a web framework displays on an HTTP response or where operational logs are directed, so it cannot close the gap between user-facing text and backend retention.
Reach for Security Review (waybarrios) when
There is a pull request waiting and the release is in an hour. I do not want a report about the whole repo — just tell me whether anything in THESE changes is actually exploitable.
All four are security reviewers, so the question is scope. waybarrios reads only the unmerged commits on the branch and reports concrete exploitation paths, which is precisely a pre-merge decision. Sentry's scans project source and jeffallan produces a prioritised whole-system audit — both answer a bigger question than the one asked, and both cost more than an hour. affaan-m is design-time guidance for code you have not written yet, which is the wrong direction entirely once the PR exists.
What they have in common
Both are filed under Security, the axis along which they collide. That shared ground is what makes an agent pick between them on description alone — and what makes it pick wrong.
Nearby comparisons
Reading the difference is not the same as spotting it at speed. That is the game.
Today's session