Agent Skills › warpdotdev/oz-for-oss › review-pr-local

review-pr-local

GitHub

为oz-for-oss仓库提供PR审查的特定指导，补充核心review-pr技能的可覆盖类别。涵盖用户界面文本、优雅降级及调试可观测性方面的审查标准。

.agents/skills/review-pr-local/SKILL.md warpdotdev/oz-for-oss

Trigger Scenarios

针对oz-for-oss仓库的代码审查需要符合特定仓库规范的PR审核

Install

npx skills add warpdotdev/oz-for-oss --skill review-pr-local -g -y

More Options

Non-standard path

npx skills add https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/review-pr-local -g -y

Use without installing

npx skills use warpdotdev/oz-for-oss@review-pr-local

指定 Agent (Claude Code)

npx skills add warpdotdev/oz-for-oss --skill review-pr-local -a claude-code -g -y

安装 repo 全部 skill

npx skills add warpdotdev/oz-for-oss --all -g -y

预览 repo 内 skill

npx skills add warpdotdev/oz-for-oss --list

SKILL.md

Frontmatter

{
    "name": "review-pr-local",
    "description": "Repo-specific review guidance for oz-for-oss. Only the categories declared overridable by the core review-pr skill may be specialized here.",
    "specializes": "review-pr"
}

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.