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

review-spec-local

GitHub

为oz-for-oss仓库提供规格文档审查指南，补充核心审查技能的特定领域要求。明确PR中product.md和tech.md的内容规范、GitHub Issue引用方式及内部链接格式标准。

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

Trigger Scenarios

审查包含product.md和tech.md的规格文档PR 验证规格文档中的问题描述、技术方案及链接规范性

Install

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

More Options

Non-standard path

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

Use without installing

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

指定 Agent (Claude Code)

npx skills add warpdotdev/oz-for-oss --skill review-spec-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-spec-local",
    "description": "Repo-specific spec-review guidance for oz-for-oss. Only the categories declared overridable by the core review-spec skill may be specialized here.",
    "specializes": "review-spec"
}

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

This file is a companion to the core review-spec 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.

Required spec sections in this repository

Spec pull requests in this repo land under specs/GH<issue-number>/ and typically include both a product.md and a tech.md. When reviewing, check that:

product.md clearly states the problem, goals, non-goals, user experience, and validation plan
tech.md clearly states the problem, relevant code, current state, proposed changes, risks, and follow-ups
both files reference the originating GitHub issue by number in the top-level heading
internal links reference files and line ranges using the repo-root-relative convention (for example path/file:line or path/file (start-end))

Linking conventions

Prefer repo-root-relative links over absolute filesystem paths in spec prose.
When a spec references another spec in the same repository, link to it via its relative path under specs/.