agentsclimarketplace
Sign in

Pull request review

Skill bakerstreetco/skills/pull-request-review

Review code changes with a bug-first engineering stance. Use when asked to review a pull request, branch diff, staged changes, patch, or recent commit for regressions, missing tests, risky behavior, incorrect assumptions, or maintainability issues.From its SKILL.md

Install
npx -y skills add bakerstreetco/skills --skill pull-request-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 315 tokens by cl100k_base, as published. Nobody here has run it

Pull Request Review

Use this skill to review changes as if they are about to merge. Prioritize correctness, regressions, security, data loss, compatibility, and missing tests over style preferences.

Workflow

  1. Inspect repository instructions and the target diff before forming conclusions.
  2. Determine the intended behavior from the issue, PR description, commit messages, changed files, and nearby code.
  3. Review changed code paths and their callers, not only the edited lines.
  4. Check tests, docs, migrations, generated files, and release notes when relevant.
  5. Run focused verification when practical, or state clearly what was not run.
  6. Report only actionable findings. Avoid low-value nits unless they mask a real bug.

Review Checks

  • Correctness: edge cases, null/empty states, concurrency, error handling, time zones, ordering, and resource cleanup.
  • Compatibility: public API changes, schema changes, migration safety, CLI flag behavior, config defaults, and persisted data.
  • Security: auth, permissions, secrets, injection, unsafe deserialization, logs, and dependency exposure.
  • Testing: missing regression tests, weak assertions, untested failure paths, and brittle fixtures.
  • Maintainability: misplaced ownership, unclear names, excessive coupling, and comments that no longer match behavior.

Output

Lead with findings ordered by severity. Each finding should include a tight file/line reference when possible, the impact, and the concrete fix direction.

If there are no findings, say so directly and mention any residual risk or verification gap.

What ships with it: 2 files

667 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 625,150. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.