$npx -y skills add warpdotdev/oz-for-oss --skill review-spec-localRepo-specific spec-review guidance for oz-for-oss. Only the categories declared overridable by the core review-spec skill may be specialized here.
| 1 | # Repo-specific spec-review guidance for `oz-for-oss` |
| 2 | |
| 3 | This file is a companion to the core `review-spec` skill. It does not |
| 4 | redefine the review output schema, severity labels, safety rules, or |
| 5 | evidence rules. It only specializes the override categories the core |
| 6 | skill marks as overridable. |
| 7 | |
| 8 | ## Required spec sections in this repository |
| 9 | |
| 10 | Spec pull requests in this repo land under `specs/GH<issue-number>/` and |
| 11 | typically include both a `product.md` and a `tech.md`. When reviewing, check that: |
| 12 | |
| 13 | - `product.md` clearly states the problem, goals, non-goals, user experience, and validation plan |
| 14 | - `tech.md` clearly states the problem, relevant code, current state, proposed changes, risks, and follow-ups |
| 15 | - both files reference the originating GitHub issue by number in the top-level heading |
| 16 | - internal links reference files and line ranges using the repo-root-relative convention (for example ``path/file:line`` or ``path/file (start-end)``) |
| 17 | |
| 18 | ## Linking conventions |
| 19 | |
| 20 | - Prefer repo-root-relative links over absolute filesystem paths in spec prose. |
| 21 | - When a spec references another spec in the same repository, link to it via its relative path under `specs/`. |