sd0x-dev-flow

Plugin sd0x-dev-flow from marketplace sd0xdev-marketplace in sd0xdev/sd0x-harness. Commands read from the repo's manifest — 1 month ago.

Skills (102)

• adr

  Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/<feature>/adr-<NNN>-<title>.md with a 3-digit zero-padded number. Handles the Superseded case: bidirectional linking when a new ADR replaces an old one. Use w

• agentctl-setup

  Install and set up the optional agentctl mod (task scope, refusal before execution, evidence that goes stale, model-free hand-over) — checks the environment, installs after approval, builds the first task line, optional deny rules, uninstall

• architecture

  Architecture design and documentation. Produces 3-architecture.md with component diagrams, data flow, integration points, and architecture decisions. Reads existing tech-spec as input. Use when: designing system architecture, documenting component interactions, creating architecture docs, producing

• ask

  Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not for: code changes (use feature-dev), code review (use codex-review-fast), deep research (use deep-research), full code trace (use code-explor

• 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 qualit

• bug-fix

  Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore). Output: fix + regression test + review gate.

• bump-version

  Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says 'bump version', 'update version', '更新版本', '版本 +1', or /bump-version

• check-coverage

  Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.

• claude-health

  Claude Code config health check + plugin sync. Use when: auditing .claude/ structure, checking naming, verifying hook setup, detecting plugin version drift, syncing installed assets. Not for: skill quality (use skill-health-check), code review (use codex-code-review). Output: health report + fix rec

• code-explore

  Pure Claude code investigation. Use when: tracing execution paths, understanding architecture, diagnosing issues. Not for: dual-perspective review (use code-investigate), code review (use codex-code-review). Output: analysis report with findings.

• code-investigate

  Dual-perspective code investigation. Use when: deep code analysis needing both Claude and Codex perspectives. Not for: quick exploration (use code-explore), code review (use codex-code-review). Output: integrated findings from dual analysis.

• codex-architect

  Codex architecture consulting. Use when: designing features, evaluating architecture, getting second opinion on design. Not for: implementation (use codex-implement), code review (use codex-code-review). Output: architecture advice + design recommendations.

• 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.

• 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.

• codex-code-review

  Code review using Codex exec. Use when: PR review, code audit, second opinion on changes. Not for: doc review (use doc-review), security audit (use security-review). Output: severity-grouped findings + merge gate.

• codex-explain

  Explain complex code via Codex exec. Use when: understanding complex logic, tracing data flow, onboarding to unfamiliar code. Not for: code review (use codex-code-review), exploration (use code-explore). Output: structured explanation at chosen depth.

• codex-implement

  Implement features via Codex exec. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop.

• codex-review-branch

  Fully automated review of an entire feature branch using Codex exec

• codex-review-doc

  Review documents using Codex exec. Supports review loop with context preservation.

• codex-review-fast

  Quick second-opinion using Codex exec (diff only, no tests). Supports review loop with context preservation.

• codex-review

  Full second-opinion using Codex exec (with lint:fix + build). Supports review loop with context preservation.

• codex-security

  OWASP Top 10 security review using Codex exec. Supports review loop with context preservation.

• codex-setup

  Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.

• codex-test-gen

  Generate unit tests for specified functions using Codex exec

• codex-test-review

  Review test case sufficiency using Codex exec, suggest additional edge cases. Supports review loop with context preservation.

• contract-decode

  EVM contract error and calldata decoder. Use when: user pastes hex revert data, calldata, function selector, or mentions custom error, execution reverted, 4byte, decode. Input contains 0x + 8+ hex chars.

• create-pr

  Create or update GitHub PR with gh CLI. Auto-extracts ticket ID from branch name, generates title/summary from commits. Auto-detects existing PR and switches to update mode. Supports --stack for stacked PR chains (per-layer PRs with chained bases; never executes push/rebase). Default: --dry-run (sho

• create-request

  Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking reques

• de-ai-flavor

  Remove AI artifacts from documents. Use when: cleaning AI-generated text, removing tool names, fixing boilerplate patterns. Not for: doc review (use doc-review), doc refactoring (use doc-refactor). Output: cleaned document preserving original intent.

• 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 + ro

• deep-analyze

  Deep-dive analysis of an initial proposal — research code implementation, produce an actionable roadmap and alternatives

• deep-explore

  Multi-wave parallel code exploration orchestrator. Use when: large-scale codebase research, understanding complex cross-domain systems, deep investigation needing multiple perspectives simultaneously. Not for: quick lookup (use code-explore), dual confirmation (use code-investigate), code review (us

• deep-research

  Universal multi-source research orchestration. Use for any research/investigate/analyze request needing synthesis across web, codebase, and community evidence — especially broad, mixed, or ambiguous intent. Triggers on: 'research this', 'deep research', 'investigate', 'analyze from multiple angles',

• dep-audit

  Audit dependency security risks

• deploy-flow

  Run the release flow a project declares in rules/git-workflow-project.md § Deploy Workflow: its git merge steps, and — only where § Run Steps is execute — its scripts, each after its own approval. Use when: the user asks to release, deploy, promote a branch, or run the project's deploy workflow. Not

• dev-security-audit

  Comprehensive developer workstation security audit — scans for exposed credentials, compromised application data, persistence mechanisms, and supply chain attack indicators. Use this skill whenever the user suspects their machine may be compromised, wants to check for exposed secrets, asks about sup

• doc-refactor

  Refactor documents — simplify without losing information, visualize flows with sequenceDiagram.

• doc-review

  Document review via Codex exec. 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.

• epic-merge

  Sequential squash-merge of stacked PR chains into an epic branch. Handles dependency-ordered rebase, collision-safe backup tags, CI monitoring (delegates to /watch-ci), and post-merge verification. Use when: merging a chain of stacked PRs into an epic branch, collapsing a linear PR stack into per-PR

• 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.

• 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.

• feature-verify

  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

• fp-brief

  First-principles briefing from technical documents. Use when: understanding why decisions were made, onboarding to feature reasoning, reviewing decision chains, explaining doc from first principles. Not for: PM/CTO summary (use project-brief), pre-doc analysis (use feasibility-study), code explanati

• generate-runner

  Generate a customized precommit runner for any ecosystem. Use when: non-Node projects need a runner, eject from generic runner, customize runner for project. Not for: running precommit (use /precommit), installing runner (handled by auto-install). Output: customized runner script with eject header.

• gh-stack

  Native stacked pull requests through the github/gh-stack extension. Detects the extension, installs it only after the user approves, resolves the branch chain, and executes `gh stack link` / `gh stack push` / `gh stack submit --auto` under a per-use AskUserQuestion gate. Use when: opening or refresh

• git-investigate

  Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.

• git-profile

  Git identity and GPG signing profile manager. Discovers profiles from GPG + git config, switches local identity, checks signing health. Use when: user says 'switch identity', 'git profile', 'check signing', 'gpg key status', 'which identity', or /git-profile

• install-hooks

  Install plugin hooks into project .claude/ for persistent use without plugin loaded

• install-rules

  Install plugin rules into project .claude/rules/ for persistent use without plugin loaded

• install-scripts

  Install plugin runner scripts into project .claude/scripts/ for persistent use without plugin loaded

• issue-analyze

  GitHub Issue and PR review thread deep analysis with Codex blind verdict. Use when: analyzing issue root cause, classifying problems, investigation planning, triaging PR review comments for actionability. Not for: fixing bugs (use bug-fix), code exploration (use code-explore). Output: classified ana

• jira

  Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).

• load-pr-review

  Load GitHub PR review comments into AI session — analyze, triage, plan. Default: analysis-only (no auto-fix). Use when: reviewing PR feedback, planning fixes, addressing review comments, replying to reviewers. Not for: creating reviews (use codex-review-fast), creating PRs (use create-pr), viewing P

• merge-prep

  Pre-merge analysis and preparation. Analyzes source branch vs target branch: commit stats, conflict detection, file impact. Analysis-only v1 — outputs report + suggested commands, does not auto-merge. Use when: user says 'merge prep', 'pre-merge', 'merge analysis', or /merge-prep

• necessity-audit

  Necessity audit for over-designed spec elements. Use when: auditing lifecycle spec (1-requirements / 2-tech-spec / 3-architecture) for YAGNI/KISS violations, challenging necessity of FRs/NFRs/abstractions/configs via Codex adversarial debate. Not for: FP reasoning validity (use /codex-review-spec),

• next-step

  Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with

• 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: vaul

• 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

• orchestrate

  Agent-driven workflow orchestration (v1 report-only). Use when: declaring an intent (audit/research/feature shape) and wanting a planner agent to derive the skill workflow, preview it, and run read-only fanout with fail-closed no-change verification. Not for: executing mutating steps (v1 emits them

• plan-review

  Pre-ExitPlanMode adversarial plan review loop via Codex exec. Use when: in plan mode, before presenting a plan to the user; reviewing an in-context plan draft. Not for: .md file review (use doc-review), code review (use codex-code-review), lifecycle spec review (use review-spec). Output: review trai

• portfolio

  Portfolio system knowledge base. Use when: position queries, routing strategy questions, provider integration. Not for: general code exploration (use code-explore), code review (use codex-code-review). Output: domain-specific analysis + recommendations.

• post-dev-recap

  Post-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. Not for: generating only a doc (use /recap-doc), Q&A over an existing recap (use /recap-ask), technical share-out (us

• post-dev-test

  Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.

• pr-comment

  Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summa

• pr-review
• pr-summary
• pre-pr-audit
• precommit-fast
• precommit
• project-audit
• project-brief
• project-setup
• push-ci
• recap-ask
• recap-doc
• refactor
• remind
• repo-intake
• req-analyze
• request-tracking
• review-spec
• risk-assess
• runbook
• safe-remove
• security-review
• seek-verdict
• sharingan
• simplify
• skill-health-check
• smart-commit
• smart-rebase
• statusline-config
• tech-brief
• tech-spec
• test-deep
• test-health
• test-review
• ui-first-principles
• update-docs
• verify
• watch-ci
• zh-tw

Subagents (16)

• architecture-designer

  Architecture design expert. Synthesizes code analysis, tech-spec context, and architecture advice into structured architecture documents with component diagrams, data flows, and architecture decisions.

• brief-writer

  PM/CTO executive summary expert. Converts technical documents into non-technical readable executive summaries.

• code-simplifier

  Cleanup refactoring expert. Simplifies code, eliminates duplication, preserves behavior.

• codex-architect

  Codex architecture consulting expert (third brain). Uses Codex CLI to obtain architecture advice and integrates dual perspectives.

• codex-implementer

  Codex implementation expert. Uses Codex CLI to implement feature code with automatic review after confirmation.

• contract-neutral-reviewer

  Contract-neutral fallback reviewer. Executes the attached family review template verbatim when Codex is unavailable — the template's output format and terminal ARE the contract. Independent research, no fed conclusions.

• coverage-analyst

  Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.

• doc-refactor

  Document refactoring expert. Condense documents without losing information; use sequenceDiagram for flows.

• feasibility-analyst

  Feasibility analysis expert. Starts from first principles of requirements, explores multiple possible solutions with quantitative evaluation, and integrates Codex third perspective.

• git-investigator

  Code archaeology expert. Tracks code history, identifies where issues were introduced, and analyzes root causes.

• performance-optimizer

  Performance optimization expert. Identifies N+1 queries, memory leaks, and slow queries.

• refactor-reviewer

  Refactoring review expert. Evaluates refactoring risk and verifies behavior preservation.

• solution-architect

  Solution deepening expert. Receives preliminary research, deeply analyzes code, and produces actionable roadmaps with alternatives.

• strict-reviewer

  Strict code reviewer. Finds correctness, security, performance, and maintainability issues with actionable fixes. Use proactively after code changes.

• tech-spec-reviewer

  Technical spec review expert. Reviews technical documents for completeness, feasibility, and risk assessment, and provides improvement suggestions.

• verify-app

  Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.

Hooks (8)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/namespace-hint.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/post-compact-auto-loop.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/pre-edit-guard.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/pre-bash-codex-launch-guard.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/post-edit-format.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/post-skill-auto-loop.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/stop-guard.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/user-prompt-review-guard.sh

Similar plugins