all publishers

sd0xdev

@sd0xdev source repo

197 published skills · page 2 of 2

  1. ▌
    Generate Runner 2 · sd0xdev bundle
    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.
    194 repo stars
  2. ▌
    Git Investigate 2 · sd0xdev bundle
    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.
    194 repo stars
  3. ▌
    Install Scripts 2 · sd0xdev
    Install plugin runner scripts into project .claude/scripts/ for persistent use without plugin loaded
    194 repo stars
  4. ▌
    Necessity Audit 2 · sd0xdev bundle
    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), completeness check (use /feature-completeness), detail review (use /codex-review-doc), or code-level simplification (use /simplify).
    194 repo stars
  5. ▌
    Security Review 2 · sd0xdev bundle
    Security review via Codex exec. Use when: OWASP Top 10:2025 audit, dependency vulnerability check, security-sensitive changes. Not for: code review (use codex-code-review), test review (use test-review). Output: security findings + audit report.
    194 repo stars
  6. ▌
    Code Investigate 2 · sd0xdev bundle
    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.
    194 repo stars
  7. ▌
    Codex Brainstorm 2 · sd0xdev bundle
    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.
    194 repo stars
  8. ▌
    Codex CLI Review 2 · sd0xdev bundle
    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.
    194 repo stars
  9. ▌
    Codex Review Doc 2 · sd0xdev
    Review documents using Codex exec. Supports review loop with context preservation.
    194 repo stars
  10. ▌
    Request Tracking 2 · sd0xdev bundle
    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.
    194 repo stars
  11. ▌
    Codex Code Review 2 · sd0xdev bundle
    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.
    194 repo stars
  12. ▌
    Codex Review Fast 2 · sd0xdev
    Quick second-opinion using Codex exec (diff only, no tests). Supports review loop with context preservation.
    194 repo stars
  13. ▌
    Codex Test Review 2 · sd0xdev
    Review test case sufficiency using Codex exec, suggest additional edge cases. Supports review loop with context preservation.
    194 repo stars
  14. ▌
    Feasibility Study 2 · sd0xdev bundle
    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.
    194 repo stars
  15. ▌
    Statusline Config 2 · sd0xdev bundle
    Customize Claude Code statusline. Use when: user says 'statusline', 'status line', 'customize statusline', 'modify statusline', 'statusline settings', 'statusline theme', 'change theme', 'color scheme', wants to add/remove/change segments (cost, git, model, context), switch color themes (catppuccin, dracula, nord), or asks what can be shown in the statusline.
    194 repo stars
  16. ▌
    Dev Security Audit 2 · sd0xdev bundle
    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 supply chain attacks, or wants a full security audit of their development environment. Also triggers on: 'am I compromised', 'check my security', 'scan for leaked keys', 'credential audit', 'supply chain attack', 'supply chain check', 'check if I was hacked'.
    194 repo stars
  17. ▌
    Skill Health Check 2 · sd0xdev bundle
    Validate skill quality against routing, progressive loading, and verification criteria. Use when: auditing skills, checking skill health, reviewing skill design. Not for: code review (use codex-code-review) or doc review (use doc-review). Output: health report with per-skill ratings + Gate.
    194 repo stars
  18. ▌
    Codex Review Branch 2 · sd0xdev
    Fully automated review of an entire feature branch using Codex exec
    194 repo stars
  19. ▌
    UI First Principles 2 · sd0xdev bundle
    First-principles UI/IA reasoning: turns a `<scenario>` + API field set into JTBD analysis, principle-anchored field-priority decisions, anti-pattern findings, and a bidirectional UI↔API gap report. Trigger: UI、UX、資訊架構、IA、scenario-driven UI、欄位優先級、information hierarchy. Not for: visual/CSS work (use `/frontend-design`), post-build critique (use `/critique`), or simplifying existing layouts (use `/distill`).
    194 repo stars
  20. ▌
    Portfolio · sd0xdev bundle
    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.
    194 repo stars
  21. ▌
    Pr Review · sd0xdev
    PR self-review — review changes, produce checklist, update rules
    194 repo stars
  22. ▌
    Precommit · sd0xdev
    Pre-commit checks — lint:fix -> build -> test
    194 repo stars
  23. ▌
    Recap Ask · sd0xdev bundle
    Interactive Q&A over an existing recap document. Use when: user wants to ask follow-up questions about a briefing-recap-<date>.md produced by /recap-doc, with recap-bounded context + out-of-scope redirect + optional promote-to-request. Not for: generating a new recap (use /recap-doc), general project Q&A (use /ask), code tracing (use /code-explore). Output: per-turn answer referencing file:line + end-of-session promote prompt.
    194 repo stars
  24. ▌
    Recap Doc · sd0xdev bundle
    Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code explanation (use /codex-explain). Output: briefing-recap-<YYYY-MM-DD>.md with file-level walkthrough, design intents, spec drift, blind spots (mandatory), and anticipated questions.
    194 repo stars
  25. ▌
    Sharingan · sd0xdev bundle
    Replicate knowledge from any source as sd0x-dev-flow skill definition. Use when: copying skills from repos, adapting patterns from articles/papers/code, converting knowledge to skill format. Not for: research without skill output (use deep-research), creating skills from scratch (use skill-creator), project onboarding (use repo-intake). Output: analysis report + generated SKILL.md files with 3-layer validation.
    194 repo stars
  26. ▌
    Tech Spec · sd0xdev bundle
    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.
    194 repo stars
  27. ▌
    Merge Prep · sd0xdev bundle
    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
    194 repo stars
  28. ▌
    Op Session · sd0xdev bundle
    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.
    194 repo stars
  29. ▌
    Pr Comment · sd0xdev bundle
    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-summary).
    194 repo stars
  30. ▌
    Pr Summary · sd0xdev bundle
    List open PRs, filter automation PRs, group by ticket ID, format as Markdown. Use when: user asks for PR summary, PR status, or /pr-summary
    194 repo stars
  31. ▌
    Tech Brief · sd0xdev bundle
    Technical briefing for developer sharing. Use when: sharing implementation findings with technical colleagues, post-development knowledge transfer, documenting what was built and why. Not for: PM/CTO summary (use project-brief), first-principles reasoning (use fp-brief), design-phase specs (use tech-spec). Output: 6-section technical brief with source provenance.
    194 repo stars
  32. ▌
    Git Profile · sd0xdev bundle
    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
    194 repo stars
  33. ▌
    Orchestrate · sd0xdev bundle
    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 as proposed-manual), code review (use codex-review-fast), doc review (use codex-review-doc). Output: plan preview + run summary + report via existing doc-review loop.
    194 repo stars
  34. ▌
    Plan Review · sd0xdev bundle
    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 trail summary + plan gate (✅ Plan Ready / ⛔ Plan Blocked / ⚠️ Plan Needs Human).
    194 repo stars
  35. ▌
    Repo Intake · sd0xdev bundle
    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.
    194 repo stars
  36. ▌
    Req Analyze · sd0xdev bundle
    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).
    194 repo stars
  37. ▌
    Review Spec · sd0xdev
    Review technical spec documents from completeness, feasibility, risk, and code consistency perspectives.
    194 repo stars
  38. ▌
    Risk Assess · sd0xdev bundle
    Uncommitted code risk assessment with breaking change detection, blast radius analysis, and scope metrics. Use when: evaluating PR risk, pre-commit risk check, large refactoring review. Not for: security vulnerabilities (use /codex-security), code correctness (use /codex-review-fast). Output: 3-dimension weighted score + risk level + gate.
    194 repo stars
  39. ▌
    Safe Remove · sd0xdev bundle
    Safely remove plugin assets (skill/agent/rule/script/hook) with dependency detection and reference cleanup. Use when: user says 'remove skill', 'delete skill', 'deprecate', 'clean up unused', or /safe-remove. Not for: code refactoring (use /simplify), feature removal requiring architecture changes (manual).
    194 repo stars
  40. ▌
    Test Health · sd0xdev bundle
    Holistic test coverage measurement. Use when: assessing test health, measuring coverage trends, quantitative + qualitative test audit. Not for: running tests (use verify), reviewing test sufficiency only (use codex-test-review), generating tests (use codex-test-gen). Output: multi-dimensional dashboard with coverage metrics + test inventory + trend.
    194 repo stars
  41. ▌
    Update Docs · sd0xdev
    Research current code state then update corresponding docs, ensuring docs stay in sync with code.
    194 repo stars
  42. ▌
    Architecture · sd0xdev bundle
    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 3-architecture.md. Not for: tech spec writing (use tech-spec), code implementation (use feature-dev), architecture consulting only (use codex-architect).
    194 repo stars
  43. ▌
    Code Explore · sd0xdev bundle
    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.
    194 repo stars
  44. ▌
    Codex Review · sd0xdev
    Full second-opinion using Codex exec (with lint:fix + build). Supports review loop with context preservation.
    194 repo stars
  45. ▌
    De AI Flavor · sd0xdev
    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.
    194 repo stars
  46. ▌
    Deep Analyze · sd0xdev
    Deep-dive analysis of an initial proposal — research code implementation, produce an actionable roadmap and alternatives
    194 repo stars
  47. ▌
    Deep Explore · sd0xdev bundle
    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 (use codex-code-review). Output: unified exploration report with completeness scoring.
    194 repo stars
  48. ▌
    Doc Refactor · sd0xdev
    Refactor documents — simplify without losing information, visualize flows with sequenceDiagram.
    194 repo stars
  49. ▌
    Obsidian CLI · sd0xdev bundle
    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.
    194 repo stars
  50. ▌
    Seek Verdict · sd0xdev bundle
    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.
    194 repo stars
  51. ▌
    Codex Explain · sd0xdev bundle
    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.
    194 repo stars
  52. ▌
    Deep Research · sd0xdev bundle
    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', 'comprehensive analysis', 'explore this topic', 'study', 'survey the landscape', 'look into', 'understand deeply', '了解', '調查', '分析', '研究'. When intent is clearly single-dimension (code-only tracing, checklist-style compliance audit, or bounded option-ranking), dispatcher may prefer a narrower skill. Otherwise route here. Supports low/medium/high budget tiers.
    194 repo stars
  53. ▌
    Install Hooks · sd0xdev
    Install plugin hooks into project .claude/ for persistent use without plugin loaded
    194 repo stars
  54. ▌
    Issue Analyze · sd0xdev bundle
    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 analysis + verdict assessment + investigation strategy.
    194 repo stars
  55. ▌
    Post Dev Test · sd0xdev bundle
    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.
    194 repo stars
  56. ▌
    Project Audit · sd0xdev bundle
    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.
    194 repo stars
  57. ▌
    Project Brief · sd0xdev
    Convert a technical spec into a PM/CTO-readable executive summary. Simplify technical details, focus on business value.
    194 repo stars
  58. ▌
    Best Practices · sd0xdev bundle
    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).
    194 repo stars
  59. ▌
    Check Coverage · sd0xdev
    Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.
    194 repo stars
  60. ▌
    Codex Security · sd0xdev
    OWASP Top 10 security review using Codex exec. Supports review loop with context preservation.
    194 repo stars
  61. ▌
    Codex Test Gen · sd0xdev
    Generate unit tests for specified functions using Codex exec
    194 repo stars
  62. ▌
    Create Request · sd0xdev bundle
    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 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: request ticket with status tracking, referencing parent tech-spec.
    194 repo stars
  63. ▌
    Feature Verify · sd0xdev bundle
    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).
    194 repo stars
  64. ▌
    Post Dev Recap · sd0xdev
    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 (use /tech-brief), first-principles reasoning of an existing doc (use /fp-brief), general code tracing (use /code-explore). Output: ScopeReport → briefing-recap-<date>.md → interactive Q&A session.
    194 repo stars
  65. ▌
    Precommit Fast · sd0xdev
    Quick pre-commit checks — lint:fix -> test
    194 repo stars
  66. ▌
    Codex Architect · sd0xdev bundle
    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.
    194 repo stars
  67. ▌
    Codex Implement · sd0xdev bundle
    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.
    194 repo stars
  68. ▌
    Contract Decode · sd0xdev bundle
    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.
    194 repo stars
  69. ▌
    Generate Runner · sd0xdev bundle
    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.
    194 repo stars
  70. ▌
    Git Investigate · sd0xdev bundle
    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.
    194 repo stars
  71. ▌
    Install Scripts · sd0xdev
    Install plugin runner scripts into project .claude/scripts/ for persistent use without plugin loaded
    194 repo stars
  72. ▌
    Necessity Audit · sd0xdev bundle
    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), completeness check (use /feature-completeness), detail review (use /codex-review-doc), or code-level simplification (use /simplify).
    194 repo stars
  73. ▌
    Security Review · sd0xdev bundle
    Security review via Codex exec. Use when: OWASP Top 10:2025 audit, dependency vulnerability check, security-sensitive changes. Not for: code review (use codex-code-review), test review (use test-review). Output: security findings + audit report.
    194 repo stars
  74. ▌
    Code Investigate · sd0xdev bundle
    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.
    194 repo stars
  75. ▌
    Codex Brainstorm · sd0xdev bundle
    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.
    194 repo stars
  76. ▌
    Codex CLI Review · sd0xdev bundle
    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.
    194 repo stars
  77. ▌
    Codex Review Doc · sd0xdev
    Review documents using Codex exec. Supports review loop with context preservation.
    194 repo stars
  78. ▌
    Request Tracking · sd0xdev bundle
    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.
    194 repo stars
  79. ▌
    Codex Review Fast · sd0xdev
    Quick second-opinion using Codex exec (diff only, no tests). Supports review loop with context preservation.
    194 repo stars
  80. ▌
    Codex Test Review · sd0xdev
    Review test case sufficiency using Codex exec, suggest additional edge cases. Supports review loop with context preservation.
    194 repo stars
  81. ▌
    Feasibility Study · sd0xdev bundle
    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.
    194 repo stars
  82. ▌
    Statusline Config · sd0xdev bundle
    Customize Claude Code statusline. Use when: user says 'statusline', 'status line', 'customize statusline', 'modify statusline', 'statusline settings', 'statusline theme', 'change theme', 'color scheme', wants to add/remove/change segments (cost, git, model, context), switch color themes (catppuccin, dracula, nord), or asks what can be shown in the statusline.
    194 repo stars
  83. ▌
    Dev Security Audit · sd0xdev bundle
    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 supply chain attacks, or wants a full security audit of their development environment. Also triggers on: 'am I compromised', 'check my security', 'scan for leaked keys', 'credential audit', 'supply chain attack', 'supply chain check', 'check if I was hacked'.
    194 repo stars
  84. ▌
    Skill Health Check · sd0xdev bundle
    Validate skill quality against routing, progressive loading, and verification criteria. Use when: auditing skills, checking skill health, reviewing skill design. Not for: code review (use codex-code-review) or doc review (use doc-review). Output: health report with per-skill ratings + Gate.
    194 repo stars
  85. ▌
    Codex Review Branch · sd0xdev
    Fully automated review of an entire feature branch using Codex exec
    194 repo stars
  86. ▌
    UI First Principles · sd0xdev bundle
    First-principles UI/IA reasoning: turns a `<scenario>` + API field set into JTBD analysis, principle-anchored field-priority decisions, anti-pattern findings, and a bidirectional UI↔API gap report. Trigger: UI、UX、資訊架構、IA、scenario-driven UI、欄位優先級、information hierarchy. Not for: visual/CSS work (use `/frontend-design`), post-build critique (use `/critique`), or simplifying existing layouts (use `/distill`).
    194 repo stars
  87. ▌
    Adr · sd0xdev bundle
    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 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 /tech-spec), task progress tracking (use /create-request), bulk backfill of historical decisions (a separate request — this skill writes one ADR at a time).
    194 repo stars
  88. ▌
    Ask · sd0xdev bundle
    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-explore). Output: structured answer with source attribution.
    194 repo stars
  89. ▌
    Jira · sd0xdev bundle
    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).
    194 repo stars
  90. ▌
    Zh Tw · sd0xdev
    Rewrite the previous reply in Traditional Chinese
    194 repo stars
  91. ▌
    Remind · sd0xdev bundle
    Lightweight model correction with context-aware rule loading. Use when: model forgot a rule, skipped a required step, edited code/docs without running review, needs to re-read CLAUDE.md or rules. Triggers on: 'you forgot', 'remind', 'check rules', 'what did you miss', '你忘了', 'did you skip review', 'why didn't you run precommit', or /remind. Also use PROACTIVELY after editing files if unsure whether auto-loop was followed — the detection prelude is cheap and catches drift early — the corrections it then runs cost what those reviews cost. Not for: full code review (use codex-review-fast), next step advice (use next-step), workflow progression (use feature-dev).
    194 repo stars
  92. ▌
    Runbook · sd0xdev bundle
    Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
    194 repo stars
  93. ▌
    Fp Brief · sd0xdev bundle
    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 explanation (use codex-explain). Output: structured reasoning chain with sensitivity analysis.
    194 repo stars
  94. ▌
    Simplify · sd0xdev
    Wrap-up refactoring — simplify code, eliminate duplication, preserve behavior
    194 repo stars
  95. ▌
    Watch CI · sd0xdev
    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).
    194 repo stars
  96. ▌
    Dep Audit · sd0xdev
    Audit dependency security risks
    194 repo stars
  97. ▌
    Next Step · sd0xdev bundle
    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 commit seed.
    194 repo stars