Explore skills

Reviews open pull requests for correctness, security, and test quality. Use this skill whenever the user asks to review a PR, check a diff, look at a branch before merging, or asks whether code is safe to ship. Triggers include "review PR #", "look at this diff", "is this safe to merge", pasting a GitHub/GitLab/Bitbucket PR URL, or pasting a raw `git diff`. Focuses on blocking bugs, not style. Always runs the test suite before reporting.

Classifies an incoming support case, suggests a queue and priority, and drafts a short canned reply — always with a visible confidence score. Use when the user pastes a case body, gives a case ID, or says "where does this go?" / "triage this". Refuses when intent is ambiguous (returns `needs-human` + clarifying question). Never escalates on frustration alone.

Scans a code diff for OWASP Top-10 issues — injection, auth bypass, crypto misuse, secrets — and reports only findings with a concrete exploit path. Use when the user asks for a security review, says "look for OWASP issues", pastes auth/session/crypto/input-handling code, or asks "is this safe?". No false positives: every finding must name a reachable exploit.

Turns a branch's diffs and PR descriptions into docs and changelog entries in the project's own voice. Use when the user says "draft release notes", "update the docs", "write the changelog for v2.1", points at a branch, or gives a set of PR URLs. Never claims a feature that isn't in the diff. Breaking changes get the project's own callout style.

Generates unit tests for uncovered branches in a repo while mirroring the project's existing test conventions. Use when the user names a file or directory that needs tests, complains about low coverage, ships new code that needs tests written alongside, or asks to "add tests for X", "cover this file", or "fill coverage gaps". Learns from existing tests before writing a single line.