All authors
Claude Skills by sd0xdev
github.com/sd0xdev178 skills0 installs282 views
- Requests> **Doc class**: Request ticket (date-prefixed non-lifecycle — per `@rules/docs-numbering.md`). Per-task work breakdown unit for progress tracking. **Not** a feature-level requirements doc. > **Created**: 2026-08-07 > **Status**: Candidate Complete > **Note**: 本 feature 尚無 tech spec；實作前建議先跑 `/tech-spec` 定義 ADR 模板欄位與編號策略。 > **Priority**: P2Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-03-26 > **Status**: Candidate Complete > **Priority**: P2 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-04-08 > **Status**: In Progress > **Priority**: P2 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-03-03 > **Status**: Completed > **Priority**: P1 > **Tech Spec**: Pending > **Source**: Codex Brainstorm Nash Equilibrium (2026-03-03)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-04-01 > **Status**: In Progress > **Priority**: P1 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-03-18 > **Status**: Completed > **Priority**: P1 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md) > **Source**: 2 rounds `/best-practices` audit + `/codex-brainstorm` Nash Equilibrium (threadIds: `019d0095-6b65-7f31-90cf-d323f8a93ea4`, `019d009d-c64e-7542-b222-5d9ec3f80aaa`)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-03-19 > **Status**: Completed > **Priority**: P1 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md) > **Best Practices Audit**: Phase 4 Gap Report (conversation 2026-03-19) > **Brainstorm threadId**: `019d053d-e515-7ca2-bd8b-f676c23d9d83`Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-03-05 > **Status**: Completed > **Priority**: P1 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-03-04 > **Status**: Completed > **Priority**: P1 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md) > **Source**: Best Practices Audit + Codex Brainstorm Nash Equilibrium (2026-03-04)Votes: 0GitHub stars: 192
- Requests> **Doc class**: Request ticket (date-prefixed non-lifecycle — per `@rules/docs-numbering.md`). > **Created**: 2026-04-17 > **Status**: Candidate Complete > **Priority**: P1 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md) > **Depends On**: [T1 — Scope Detector + Redaction](./2026-04-17-t1-scope-detector-redaction-util.md) > **Requirements**: [1-requirements.md](../1-requirements.md)Votes: 0GitHub stars: 192
- Requests> **Doc class**: Request ticket (date-prefixed non-lifecycle — per `@rules/docs-numbering.md`). > **Created**: 2026-04-17 > **Status**: Candidate Complete > **Priority**: P1 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md) > **Requirements**: [1-requirements.md](../1-requirements.md)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-03-18 > **Status**: Completed > **Priority**: P1 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md) > **Source**: `/best-practices` audit + `/codex-brainstorm` Nash Equilibrium (threadId: `019cff6f-2340-7b30-aec7-256b10a90f93`)Votes: 0GitHub stars: 192
- Archived> **Created**: 2026-02-12 > **Status**: Completed > **Archived**: 2026-02-12 > **Priority**: P2 > **Tech Spec**: (pending — run `/tech-spec` to generate)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-03-19 > **Status**: Candidate Complete > **Priority**: P1 > **Deep Research**: conversation 2026-03-19 (2 agents, score 88/100)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-04-03 > **Status**: In Progress > **Priority**: P1 > **Tech Spec**: [Requirements Analysis Tech Spec](../2-tech-spec.md)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-04-07 > **Status**: In Progress > **Priority**: P1 > **Tech Spec**: [Tech Spec](../2-tech-spec.md)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-03-16 > **Status**: Completed > **Priority**: P2Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-03-09 > **Status**: Completed > **Priority**: P1 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-04-01 > **Status**: In Progress > **Priority**: P2 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-04-07 > **Status**: In Progress > **Priority**: P2 > **Tech Spec**: [tech-brief Tech Spec](../2-tech-spec.md)Votes: 0GitHub stars: 192
- Requests> **Created**: 2026-03-13 > **Status**: Completed > **Priority**: P1 > **Tech Spec**: [2-tech-spec.md](../2-tech-spec.md) > **Best Practices Audit**: Phase 4 Gap Report (conversation 2026-03-13) > **Brainstorm threadId**: `019ce580-f0c1-75a3-96cf-92b57e837ce2`Votes: 0GitHub stars: 192
- AdrWrite 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 when: recording why an architectural approach was chosen, documenting a decision so it doesn't get re-litigated, marking a prior decision as superseded. Not for: feature-level technical design (use ...Votes: 0GitHub stars: 192
- ArchitectureArchitecture 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 3-architecture.md. Not for: tech spec writing (use tech-spec), code implementation (use feature-dev), architecture consulting only (use codex-architect).Votes: 0GitHub stars: 192
- AskContext-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-explore). Output: structured answer with source attribution.Votes: 0GitHub stars: 192
- Best PracticesIndustry 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).Votes: 0GitHub stars: 192
- Bump VersionBump 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-versionVotes: 0GitHub stars: 192
- Check CoverageComprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.Votes: 0GitHub stars: 192
- Code ExplorePure 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.Votes: 0GitHub stars: 192
- Code InvestigateDual-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.Votes: 0GitHub stars: 192
- Codex ArchitectCodex 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.Votes: 0GitHub stars: 192
- Codex BrainstormAdversarial 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.Votes: 0GitHub stars: 192
- Codex Cli ReviewCode 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.Votes: 0GitHub stars: 192
- Codex Code ReviewCode 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.Votes: 0GitHub stars: 192
- Codex ExplainExplain 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.Votes: 0GitHub stars: 192
- Codex ImplementImplement 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.Votes: 0GitHub stars: 192
- Codex Review BranchFully automated review of an entire feature branch using Codex execVotes: 0GitHub stars: 192
- Codex Review DocReview documents using Codex exec. Supports review loop with context preservation.Votes: 0GitHub stars: 192
- Codex Review FastQuick second-opinion using Codex exec (diff only, no tests). Supports review loop with context preservation.Votes: 0GitHub stars: 192
- Codex ReviewFull second-opinion using Codex exec (with lint:fix + build). Supports review loop with context preservation.Votes: 0GitHub stars: 192
- Codex SecurityOWASP Top 10 security review using Codex exec. Supports review loop with context preservation.Votes: 0GitHub stars: 192
- Codex SetupInitialize 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.Votes: 0GitHub stars: 192
- Codex Test GenGenerate unit tests for specified functions using Codex execVotes: 0GitHub stars: 192
- Codex Test ReviewReview test case sufficiency using Codex exec, suggest additional edge cases. Supports review loop with context preservation.Votes: 0GitHub stars: 192
- Contract DecodeEVM 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.Votes: 0GitHub stars: 192
- Create PrCreate 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 (show command, don't execute). Use when: user asks to open/create/update a PR, says /create-pr, wants a stacked PR chain, wants to refresh PR description after new commits, or says 'update pr', 'update...Votes: 0GitHub stars: 192
- Create RequestCreate, 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 request status dashboard. Not for: feature-level problem-space analysis (use req-analyze for 1-requirements.md lifecycle doc), tech specs (use tech-spec), code implementation (use feature-dev). Output: r...Votes: 0GitHub stars: 192
- De Ai FlavorRemove 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.Votes: 0GitHub stars: 192
- DebugInteractive 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.Votes: 0GitHub stars: 192
- Deep AnalyzeDeep-dive analysis of an initial proposal — research code implementation, produce an actionable roadmap and alternativesVotes: 0GitHub stars: 192
- Deep ExploreMulti-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 (use codex-code-review). Output: unified exploration report with completeness scoring.Votes: 0GitHub stars: 192