Skip to content
Back to skills

Review Pr Local

ASecurity

Repo-specific review guidance for oz-for-oss. Only the categories declared overridable by the core review-pr skill may be specialized here.

  • 3 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 8, 2026
code-qualitygodebugging

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 8, 2026

npx -y skills add agisota/old-one --skill review-pr-local --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Review Pr Local?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Review Pr Local
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agisota-review-pr-local/badge)](https://www.skillsdirectory.com/skills/agisota-review-pr-local)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: review-pr-local
specializes: review-pr
description: Repo-specific review guidance for oz-for-oss. Only the categories declared overridable by the core review-pr skill may be specialized here.
---

# Repo-specific review guidance for `oz-for-oss`

This file is a companion to the core `review-pr` skill. It does not
redefine the review output schema, severity labels, safety rules, or
evidence rules. It only specializes the override categories the core
skill marks as overridable.

## User-facing strings

- Flag interpolated text that would read unnaturally at runtime (e.g. wrong casing after a sentence fragment like "The triage concluded that {summary}").
- Link text should be descriptive (e.g. "triage session on Warp"), not bare URLs or generic "click here" labels.
- Verify that terminology is consistent across related messages in the same PR.

## Graceful degradation

- When code renders optional dynamic data (URLs, session links, metadata), flag cases where a missing value would produce empty or broken output. The fix is usually to omit the element entirely and show a short fallback message.
- Prefer starting with generic, user-safe error messages over exposing internal details.

## Debugging and observability

- Do not suggest removing session links, workflow URLs, or other debugging context from error paths. These are valuable for post-incident investigation even when the operation failed.

Files in this skill

  • .installed-from.json301 B
  • SKILL.md1.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in code-quality →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.