Expert code-review capability pack for deterministic PR audits, risk-ranked findings, and low-noise fix planning without SaaS lock-in.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
3 prerequisites to line up before setup.
Safety & privacy surface
1 safety and 1 privacy notes across 2 risk areas. Review closely: credentials & tokens, network access.
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
# Trigger
"Apply the code review automation capability pack to this PR."
# Required output
1) Risk-ranked findings (P0-P3) with evidence
2) Exploitability notes and blast-radius estimate
3) Minimal patch plan grouped by file ownership
4) Post-fix validation checklistThis capability pack is pinned to documentation verified on 2026-04-11. Refresh references before using this skill for critical production decisions.
This skill teaches agents to perform fast, low-noise code reviews that mimic senior reviewer behavior: clear severity, concrete evidence, and fix-first recommendations.
SKILL.md.SKILL.md content as reusable workflow instructions..gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported..cursor/rules/*.mdc adapter for project rules.Issue: Too many low-signal findings
Fix: tighten rule set to changed files and critical paths first.
Issue: Security findings lack proof
Fix: require request/response, data-flow, or control-path evidence.
Issue: Patch plan is too broad
Fix: break by file ownership and dependency boundary.
Show that Code Review Automation Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/coderabbit-lite-pr-review-capability-pack)Code Review Automation Capability Pack Skill side by side with its closest alternative on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
| Field | Expert code-review capability pack for deterministic PR audits, risk-ranked findings, and low-noise fix planning without SaaS lock-in. Open dossier | Expert maintainer pull request triage capability pack for classifying open PRs, applying labels, routing reviewers, checking merge readiness, and producing privacy-safe queue summaries using GitHub pull request documentation workflows. Open dossier |
|---|---|---|
| Next stepsDiffers | ||
| Trust | ||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified2026-04-11 | Package not verified |
| Source provenanceDiffers | Source-backed | Submission linkedSource submission |
| SubmitterDiffers | — | kiannidev |
| Install risk | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — |
| Category | skills | skills |
| Source | First-party | Source-backed |
| Author | JSONbored | kiannidev |
| Added | 2026-04-11 | 2026-06-15 |
| Platforms | ||
| Harness | ||
| Source repo | — | — |
| Safety notes | ✓Installs from a downloaded package and may run local commands or scaffold files as part of the workflow; review the package and any generated changes before applying. | ✓Treat label changes, reviewer requests, milestone moves, and merge approvals as governance actions requiring maintainer approval. Do not merge or close pull requests from triage output alone unless explicit automation policy exists. Escalate suspected security, license, or conduct issues to private maintainer channels instead of public PR threads. Rate-limit bulk triage actions to avoid notification storms for contributors and reviewers. |
| Privacy notes | ✓Operates on your local project files and any context you share in the session; review what you expose before sharing — nothing is sent beyond the model unless a step calls an external service. | ✓Pull request diffs and comments can contain proprietary code, customer examples, tokens, and internal URLs. Queue summaries for shared channels should use PR numbers, labels, and blocker types—not pasted diffs or secrets. Contributor identities and employer hints in PR descriptions may be sensitive; avoid unnecessary quoting in public notes. Exported triage reports should follow repository data-retention and contributor privacy policies. |
| Prerequisites |
|
|
| Install | | — |
| Config | — | — |
| Citations | ||
| Claim | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Review AI-generated pull requests with repeatable security, test, and evidence checks.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.