Claude skill
Feature Verify
Feature Verify is a Claude skill in the Sd0x Harness plugin. Feature verification (READ-ONLY, P0-P5). Use when: verifying feature behavior after deployment, validating API responses, diagnosing production issues, post-deploy smoke test.
What it does
The description in the skill's SKILL.md, which Claude reads to decide when to use it:
Feature verification (READ-ONLY, P0-P5). Use when: verifying feature behavior after deployment, validating API responses, diagnosing production issues, post-deploy smoke test. Not for: modifying data (use feature-dev), code review (use codex-review-fast), writing tests (use codex-test-gen), security audit (use codex-security).
The skill's instructions (about 1,859 words) cover:
- Trigger
- When NOT to Use
- Core Principle
- Degradation Matrix
- Workflow
- P0: Scope & Safety
- P1: Diff-Lite Scoping
- P2: Test Charter
- P3: API Execute
- P4: Observation Correlate
- A. Per-Request Log Correlation (L1/L2 test case types, requires L3+)
- B. Time-Window Scan (all cases)
How to use it
- Feature Verify comes inside the Sd0x Harness plugin, so you get it by installing that plugin, along with its 101 other skills. A plugin installs as one unit, with all its skills. The plugin's page has the install steps, and plugins are saved to your Claude account.
- Ask Claude for the task. When your request matches the skill's description, Claude loads it.
- To pick it yourself in Claude chat, type
/or click + and choose feature-verify. In Claude Code and Cowork, type:/sd0x-dev-flow:feature-verify
Source
- Plugin
- Sd0x Harness
- SKILL.md
- View on GitHub
- Repo stars
- 196
- Repo last pushed
- Nov 16, 2026
- Checked
- Nov 16, 2026
More skills in Sd0x Harness
- Fp BriefFirst-principles briefing from technical documents.
- Generate RunnerGenerate a customized precommit runner for any ecosystem.
- Gh StackNative stacked pull requests through the github/gh-stack extension.
- Git InvestigateGit history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis.
- Git ProfileGit identity and GPG signing profile manager.
- Install HooksInstall plugin hooks into project .claude/ for persistent use without plugin loaded
- Install RulesInstall plugin rules into project .claude/rules/ for persistent use without plugin loaded
- Install ScriptsInstall plugin runner scripts into project .claude/scripts/ for persistent use without plugin loaded
- Issue AnalyzeGitHub Issue and PR review thread deep analysis with Codex blind verdict.
- JiraJira integration — view issues, generate branches, create tickets, transition status.
- Load PR ReviewLoad GitHub PR review comments into AI session — analyze, triage, plan.
- Merge PrepPre-merge analysis and preparation. Analyzes source branch vs target branch: commit stats, conflict detection, file impact.
- Necessity AuditNecessity audit for over-designed spec elements.
- Next StepChange-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree.
- Obsidian CLIObsidian vault integration via official CLI.
- Op SessionInitialize 1Password CLI session for Claude Code.
- OrchestrateAgent-driven workflow orchestration (v1 report-only).
- Plan ReviewPre-ExitPlanMode adversarial plan review loop via Codex exec.
- PortfolioPortfolio system knowledge base. Use when: position queries, routing strategy questions, provider integration.
- Post Dev RecapPost-development recap wrapper. Use when: AI/Codex just finished implementing a feature and the user wants a guided walkthrough with scope detection + doc generation + follow-up Q&A.
- Post Dev TestPost-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests.
- PR CommentPost friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review.
- PR ReviewPR self-review — review changes, produce checklist, update rules
- PR SummaryList open PRs, filter automation PRs, group by ticket ID, format as Markdown. Use when: user asks for PR summary, PR status, or /pr-summary