skills/seek-verdict/SKILL.md
Independent second-opinion verification for any finding. Use when: Claude or user wants independent Codex verification of a review finding — dismiss (false positive check), confirm (does this issue exist?), or clarify (what's the impact?). Triggers: dismiss verification, seek verdict, verify dismiss, false positive check, second opinion, confirm finding, clarify impact. Not for: general code review (use codex-code-review), architecture debates (use codex-brainstorm). Output: [DISMISS_VERDICT] or [SEEK_VERDICT] audit trail with verdict, confidence, and evidence refs.
npx skillsauth add sd0xdev/sd0x-dev-flow seek-verdictInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
/codex-review-fast)/codex-brainstorm)[NIT_DEFERRED])| Intent | Purpose | Eligible Severities | Output Token |
|--------|---------|-------------------|-------------|
| dismiss | Is this a false positive? | All (P0/P1/P2/Nit) | [DISMISS_VERDICT] |
| confirm | Does this issue actually exist? | All | [SEEK_VERDICT] |
| clarify | What's the actual impact? | All | [SEEK_VERDICT] |
Default intent: dismiss (backward compatible with v1).
| Severity | Authorization | Gate |
|----------|-------------|------|
| P0 | DISMISS_CANDIDATE | Human confirmation required |
| P1 | DISMISS_CANDIDATE | Human confirmation required |
| P2 | DISMISS_VERIFIED | Automated |
| Nit | DISMISS_VERIFIED | Automated |
P0/P1 dismiss produces a candidate, not a final authorization. See Policy Mapping for human gate protocol.
sequenceDiagram
participant C as Claude
participant S as seek-verdict
participant X as Codex (fresh thread)
C->>S: Finding + intent + severity
Note over S: Phase A: Candidate Packaging
S->>S: Extract finding_packet<br/>(no Claude conclusions)
S->>X: Phase B: Blind Independent Verdict
Note over X: Independent research<br/>git status / grep / cat
X-->>S: verdict + confidence + evidence
Note over S: Phase C: Policy Mapping (intent x severity)
alt intent=dismiss + P2/Nit
S-->>C: DISMISS_VERIFIED / FIX_REQUIRED (automated)
else intent=dismiss + P0/P1
S-->>C: DISMISS_CANDIDATE + Need Human (human gate)
else intent=confirm/clarify
S-->>C: [SEEK_VERDICT] informational result
end
Extract finding artifact from review output:
| Field | Source |
|-------|--------|
| finding_key | file + canonical_issue_text |
| severity | <P0 \| P1 \| P2 \| Nit> |
| intent | <dismiss \| confirm \| clarify> |
| original_finding_text | Codex review original (secrets redacted) |
| origin_thread_id | Review session threadId |
| current_head_sha | git rev-parse HEAD |
| relevant_diff | git diff HEAD -- <file> |
Critical: Record Claude's hypothesis locally. Never send it to Codex.
Use the prompt template in Verdict Prompt.
| Requirement | Detail |
|-------------|--------|
| Thread | Fresh mcp__codex__codex (never reuse review thread) |
| Sandbox | read-only |
| Approval policy | never |
| Anti-anchoring | No Claude conclusions in prompt |
Apply thresholds from Policy Mapping.
Dismiss intent: graduated thresholds by severity (P0: 0.95/4, P1: 0.90/3, P2: 0.80/2, Nit: 0.70/1).
Confirm intent: ACTIONABLE->CONFIRMED, NON_ACTIONABLE->DISPUTED, low confidence->UNCERTAIN.
Clarify intent: HIGH_IMPACT / LOW_IMPACT / UNCERTAIN.
Output audit trail per Policy Mapping.
If Codex returns FIX_REQUIRED and Claude has objective counter-evidence:
mcp__codex__codex-reply (same verdict thread)NEED_HUMANSee Policy Mapping for full rules.
DISMISS_VERIFIED -> [DISMISS_PATTERN_WARN] + heightened thresholdsDismiss intent:
[DISMISS_VERDICT] key=<file|canonical_issue> | severity=<P0-Nit> | verdict=<DISMISS_VERIFIED|DISMISS_CANDIDATE|FIX_REQUIRED|NEED_HUMAN> | confidence=<0..1> | codex_thread=<id> | evidence=<brief> | timestamp=<ISO8601> | intent=dismiss | authorization=<automated|human-required|human-confirmed>
Confirm/Clarify intent:
[SEEK_VERDICT] key=<file|canonical_issue> | severity=<P0-Nit> | intent=<confirm|clarify> | verdict=<CONFIRMED|DISPUTED|HIGH_IMPACT|LOW_IMPACT|UNCERTAIN> | confidence=<0..1> | codex_thread=<id> | evidence=<brief> | timestamp=<ISO8601>
dismiss / confirm / clarify)[DISMISS_VERDICT] or [SEEK_VERDICT])DISMISS_CANDIDATE + human gate (never auto-dismiss)| File | Purpose | |------|---------| | Verdict Prompt | Codex blind verification prompt template | | Policy Mapping | Intent x severity thresholds, audit format, anti-abuse |
documentation
Rewrite the previous reply in Traditional Chinese
development
Monitor GitHub Actions CI runs until completion. Use when: watching CI after push, checking build status, monitoring PR checks, waiting for CI completion, user says 'watch CI', 'check CI', 'CI status', 'monitor build', or /watch-ci. Not for: pushing code (use push-ci), creating PRs (use create-pr). Output: per-run verdict (pass/fail/timeout).
development
Verification loop — lint -> typecheck -> unit -> integration -> e2e
development
Research current code state then update corresponding docs, ensuring docs stay in sync with code.