Topic: skills
17,247 skills in this topic.
-
best-practices
Industry best practices conformance audit with mandatory adversarial debate. Produces audit artifact: verdict (OK/WARN/FAIL) + gap roadmap + debate proof. Use when: auditing current implementation against industry standards, checking compliance with best practices, benchmarking implementation quality, verifying a codebase meets a standard. Not for: broad research/discovery without audit target (use /deep-research), code review (use /codex-review), architecture design (use /codex-architect).
sd0xdev/sd0x-dev-flow 139
-
deep-analyze
Deep-dive analysis of an initial proposal — research code implementation, produce an actionable roadmap and alternatives
sd0xdev/sd0x-dev-flow 139
-
precommit
Pre-commit checks — lint:fix -> build -> test
sd0xdev/sd0x-dev-flow 139
-
feature-dev
Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.
sd0xdev/sd0x-dev-flow 139
-
codex-brainstorm
Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items.
sd0xdev/sd0x-dev-flow 139
-
op-session
Initialize 1Password CLI session for Claude Code. Use when: starting a session that needs 1Password secrets, op CLI keeps prompting biometric auth, setting up OP_SESSION token. Solves: Claude Code's no-TTY subprocess model triggers 1Password biometric auth on every op call. Supports both token-based and App Integration auth modes — auto-detects which mode to use.
sd0xdev/sd0x-dev-flow 139
-
simplify
Wrap-up refactoring — simplify code, eliminate duplication, preserve behavior
sd0xdev/sd0x-dev-flow 139
-
feasibility-study
Feasibility analysis from first principles. Use when: evaluating solutions before tech-spec, comparing approaches, risk assessment. Not for: implementation (use feature-dev), architecture advice (use codex-architect). Output: quantitative comparison + recommendation.
sd0xdev/sd0x-dev-flow 139
-
obsidian-cli
Obsidian vault integration via official CLI. Use when: capturing dev artifacts to Obsidian vault, searching vault for context, appending to daily note, managing tasks in vault. Not for: general note-taking without Obsidian (use regular files), browsing Obsidian docs (use agent-browser). Output: vault search results, captured notes, task updates.
sd0xdev/sd0x-dev-flow 139
-
codex-cli-review
Code review via Codex CLI with full disk access. Use when: deep review needing full codebase read, uncommitted change review. Not for: quick diff review (use codex-code-review), doc review (use doc-review). Output: severity-grouped findings + merge gate.
sd0xdev/sd0x-dev-flow 139
-
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
sd0xdev/sd0x-dev-flow 139
-
install-scripts
Install plugin runner scripts into project .claude/scripts/ for persistent use without plugin loaded
sd0xdev/sd0x-dev-flow 139
-
request-tracking
Request tracking knowledge base. Use when: querying request status, managing document references, tracking progress. Not for: creating requests (use create-request), tech specs (use tech-spec). Output: status report + progress tracking.
sd0xdev/sd0x-dev-flow 139
-
install-hooks
Install plugin hooks into project .claude/ for persistent use without plugin loaded
sd0xdev/sd0x-dev-flow 139
-
repo-intake
Project initialization inventory (one-time). Use when: first onboarding a project, rebuilding cache after structural changes. Not for: day-to-day development (read cache directly), finding specific files (use code-explore). Output: project map with entrypoints + test map + next steps.
sd0xdev/sd0x-dev-flow 139
-
install-rules
Install plugin rules into project .claude/rules/ for persistent use without plugin loaded
sd0xdev/sd0x-dev-flow 139
-
req-analyze
Requirements analysis — problem decomposition, stakeholder scan, requirement structuring. Produces 1-requirements.md (Phase 1 lifecycle doc, NOT the per-task request ticket — for those use /create-request). Use when: analyzing needs before tech spec, decomposing requirements, stakeholder analysis, 需求分析. Not for: solution comparison (use feasibility-study), tech design (use tech-spec), per-task tracking tickets (use create-request), issue root cause (use issue-analyze).
sd0xdev/sd0x-dev-flow 139
-
doc-review
Document review via Codex MCP. Use when: reviewing .md docs, tech spec audit, document quality check. Not for: code review (use codex-code-review), test review (use test-review). Output: 5-dimension rating table + gate.
sd0xdev/sd0x-dev-flow 139
-
codex-review-fast
Quick second-opinion using Codex MCP (diff only, no tests). Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
-
precommit-fast
Quick pre-commit checks — lint:fix -> test
sd0xdev/sd0x-dev-flow 139
-
project-audit
Project health audit with deterministic scoring. Use when: evaluating project quality, onboarding to new codebase, periodic health checks. Not for: runtime performance analysis, security-specific audits (use /codex-security). Output: 5-dimension score + actionable findings.
sd0xdev/sd0x-dev-flow 139
-
codex-security
OWASP Top 10 security review using Codex MCP. Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
-
seek-verdict
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.
sd0xdev/sd0x-dev-flow 139
-
tech-spec
Tech spec generation and review. Use when: designing features, writing specs, spec review. Not for: requirements analysis (use req-analyze), implementation (use feature-dev), architecture advice (use codex-architect). Output: numbered tech spec document.
sd0xdev/sd0x-dev-flow 139