Skip to content
Back to skills

Review Spec Local

ASecurity

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

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

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-spec-local --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Review Spec Local?

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

Security grade badge for Review Spec Local
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agisota-review-spec-local/badge)](https://www.skillsdirectory.com/skills/agisota-review-spec-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-spec-local
specializes: review-spec
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.
---

# 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/`.

Files in this skill

  • .installed-from.json303 B
  • SKILL.md1.3 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.