菜单
Adversarial spec-compliance PR review — cross-references diffs against approved specs, verifies runtime claims against source, detects competing PRs, audits scope/convention compliance. Use before merging.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill adversarial-pr-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | adversarial-pr-review |
| description | Adversarial spec-compliance PR review — cross-references diffs against approved specs, verifies runtime claims against source, detects competing PRs, audits scope/convention compliance. Use before merging. |
| version | 1.0.0 |
| user-invocable | true |
| format | "2025-10-02T00:00:00.000Z" |
| status | ACTIVE |
| updated | "2026-04-15T00:00:00.000Z" |
| triggers | ["reviewing a pull request before merge","cross-referencing a diff against an approved spec","auditing PR scope/convention compliance or detecting competing PRs"] |
Adversarial review with spec-compliance focus. Reviews PRs like a hostile-but-fair reviewer — verifies that what the PR claims matches what it actually does and what the approved spec requires.
Accept one of:
--pr <N> — review a single PR--all — review all open PRs by the current author--branch <name> — review the diff on a specific branch against mainFor each PR under review, collect:
gh pr view <N> -R Tibsfox/gsd-skill-creator --json title,body,headRefName,labels,reviewDecision,statusCheckRollup,files
Extract issue number from PR body (Closes #N, Fixes #N, Resolves #N).
gh api repos/Tibsfox/gsd-skill-creator/issues/<N> --jq '{title, labels: [.labels[].name], state, body}'
Verify:
From the issue body or PR description, extract:
gh pr list -R Tibsfox/gsd-skill-creator --state open --search "closes #<issue_number> OR fixes #<issue_number>" --json number,author,title
If multiple PRs target the same issue, flag the competition.
gh pr diff <N> -R Tibsfox/gsd-skill-creator
Or for branch mode:
git diff main...HEAD
Cross-reference every claim against reality.
Compare files in the diff against files listed in the approved issue scope:
| Check | Verdict |
|---|---|
| All in-scope files are modified | PASS / UNDER-DELIVERY |
| Only in-scope files are modified | PASS / SCOPE CREEP |
| Modifications match approved intent | PASS / DEVIATION |
For each acceptance criterion in the approved issue:
Flag any criterion that is:
When the spec defines a data schema, API interface, or config shape:
This repo has strict import boundaries (CLAUDE.md):
src/ never imports desktop/@tauri-apps/apidesktop/ never imports Node.js modulesVerify that runtime references in the code actually exist.
When the diff adds new imports:
# Check the import target exists
grep -r "export.*<name>" src/ desktop/
If the imported symbol doesn't exist, this is BLOCKING.
When code references skills (.claude/skills/) or agents (.claude/agents/):
subagent_type values in Agent calls match defined agent typesWhen code references settings or config fields:
grep -n "<field_name>" .claude/settings.json src/
Verify field names, defaults, and types match the source of truth.
When workflows reference GSD commands (.claude/commands/gsd/):
Check project conventions per CLAUDE.md.
<type>(<scope>): <subject>For test files:
import { describe, it, expect } from 'vitest'any types without justificationFor skill files in .claude/skills/:
name, description requiredversion present for versioned skillsuser-invocable: true only if the skill should be directly callable.planning/ files never committed (gitignored by design)When code interpolates values into shell commands:
When code accepts file paths:
../ traversal in user-provided paths.planning/ files are not accidentally committed.env files, credentials, API keys in the diff.gitignore covers sensitive patternsThis is a self-modifying system — skills, agents, hooks can change behavior:
Beyond spec compliance:
For each PR, produce a structured review:
## Adversarial Review — PR #<N>
### Issue Linkage
- Issue: #<N> — labels: [list] — **PASS** / **FAIL** (reason)
### Scope Compliance
| Check | Status | Detail |
|-------|--------|--------|
| All in-scope files modified | PASS/FAIL | ... |
| No out-of-scope files | PASS/FAIL | ... |
| Import boundaries respected | PASS/FAIL | ... |
### Acceptance Criteria
| Criterion | Implemented | Tested | Correct | Notes |
|-----------|-------------|--------|---------|-------|
| AC-1: ... | Yes/No | Yes/No | Yes/No | ... |
### Runtime Claims
| Claim | Verified | Detail |
|-------|----------|--------|
| Import target exists | Yes/No | ... |
| Skill reference valid | Yes/No | ... |
### Convention Compliance
| Check | Status | Detail |
|-------|--------|--------|
| Conventional Commits | PASS/FAIL | ... |
| Vitest for tests | PASS/FAIL | ... |
| No .planning/ commits | PASS/FAIL | ... |
### Security
| Finding | Severity | Detail |
|---------|----------|--------|
| ... | BLOCKING/WARNING/INFO | ... |
### Adversarial Findings
| Finding | Severity | Detail |
|---------|----------|--------|
| ... | BLOCKING/WARNING/INFO | ... |
### Competing PRs
- None / #<N> by <author> — [comparison notes]
### Verdict
**APPROVE** / **CHANGES REQUESTED** / **CLOSE** (with rationale)
### Required Changes (if any)
1. ...
### Non-blocking Observations
1. ...
Use the moment a request is underspecified and you are about to act on an ASSUMED goal. Enumerate the candidate goals the request could mean, project the action or artifact each one implies, and check whether they diverge: if two or more plausible goals lead to materially different actions or artifacts, ask exactly ONE targeted clarifying question; otherwise proceed on the most-likely goal and state the assumption in one line. Clarification is an evidence-producing action, not a delay — but one question, never an interrogation. Distinct from gsd-spec-phase (GSD-phase-bound, emits a heavy SPEC.md) and intent-router (fetch strategy, not goal disambiguation). Backed by agent goal-state inference (arxiv 2606.16813v1). Triggers on acting under an assumed goal when the request admits more than one materially different reading.
Use at write time to vector/embedding memory — Grove content-addressed insertion, chroma/pgvector upserts, memory-consolidation promoting session traces to MEMORY.md, or embedding externally-ingested content. Scores each candidate record against a fixed panel of sentinel queries and quarantines any record that would become the nearest neighbor of too many unrelated queries — a hub — whether from adversarial poisoning or accidental over-generality. This is the memory-record-side sibling of skill-injection-guardian (file-side) and the write-side complement of memory-use-warrant (read-side). Quarantine, never silently drop; a human reviews. Backed by the admission-time hubness gate (arxiv 2606.19692v1). Triggers on inserting into vector memory, consolidating memory, and embedding stranger content.
Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.