Side-by-side comparison · skills
security-review vs security-reviewer
What we have checked about each, line by line. Every value shows where it came from and when we last confirmed it.
Skills
security-review
Product management workflows for Claude Code: evidence-led briefs, discovery, and everyday PM work.
Skills
security-reviewer
67 Specialized Skills for Full-Stack Developers. Transform Claude Code into your expert pair programmer.
Checked facts
Line by line
| Measure | security-review | security-reviewer |
|---|---|---|
| Security check (static checks) | 100 out of 100 | 94 out of 100 |
| Lab structure check | Not checked yet | Structure checked |
| Days since the last commit | 14 | 3 |
| GitHub forks | 4 | 1,186 |
| GitHub stars | 22 | 12,360 |
| Open issues | 1 | 34 |
| Releases in the last 90 days | 0 | 4 |
| Days to a first reply on issues | Not checked yet | 19.9 |
A line appears only when at least one record has a value we confirmed from a source. Values we have not confirmed are left out, never guessed. Records of different types share fewer lines.
Add a third
Compare with one more record
How this works
Share it, or build your own
This page works for any two or three records in the directory, of any type. The link stays the same whichever order you name them in, so you can share it as it is. Change the records in the address, for example /directories/vs/claude-code-vs-cursor, or start from our editorial comparisons.