Sponsored by

Find leads on Reddit on auto pilot

Topic: skills

17,247 skills in this topic.

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
sd0xdev/sd0x-dev-flow 139
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 PR status (use pr-summary).
sd0xdev/sd0x-dev-flow 139
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).
sd0xdev/sd0x-dev-flow 139
skill-health-check 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.
sd0xdev/sd0x-dev-flow 139
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 analysis + verdict assessment + investigation strategy.
sd0xdev/sd0x-dev-flow 139
pr-review PR self-review — review changes, produce checklist, update rules
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
install-rules Install plugin rules into project .claude/rules/ for persistent use without plugin loaded
sd0xdev/sd0x-dev-flow 139
install-hooks Install plugin hooks into project .claude/ for persistent use without plugin loaded
sd0xdev/sd0x-dev-flow 139
codex-review Full second-opinion using Codex MCP (with lint:fix + build). Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
simplify Wrap-up refactoring — simplify code, eliminate duplication, preserve behavior
sd0xdev/sd0x-dev-flow 139
codex-implement Implement features via Codex MCP. 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.
sd0xdev/sd0x-dev-flow 139
sharingan 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.
sd0xdev/sd0x-dev-flow 139
codex-explain Explain complex code via Codex MCP. 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.
sd0xdev/sd0x-dev-flow 139
ddia-principles Designing Data-Intensive Applications (DDIA) distilled reference guide by Martin Kleppmann. MUST be loaded when: designing database schemas, choosing storage engines, implementing replication or partitioning, handling distributed transactions, building batch/stream processing pipelines, choosing consistency models, implementing consensus, designing data flow architectures, evaluating trade-offs between availability and consistency, encoding/serialization decisions, data modeling (relational vs document vs graph), building fault-tolerant systems, or any system design and architecture discussion involving data-intensive applications. Trigger on: database design, replication, partitioning, sharding, transactions, isolation levels, consistency, consensus, CAP theorem, batch processing, stream processing, MapReduce, Kafka, event sourcing, CDC, OLTP, OLAP, B-tree, LSM-tree, data warehouse, schema evolution, encoding formats, distributed systems, fault tolerance, leader election, quorum.
luoling8192/ai-coding-principles 145
ai-coding-discipline Mandatory coding discipline rules that prevent common AI coding anti-patterns. MUST be loaded for ALL code writing, editing, reviewing, bug fixing, and testing tasks. Trigger on: writing code, editing code, fixing bugs, writing tests, implementing features, refactoring, code review, creating functions, adding error handling, debugging. This skill enforces fail-fast principles, proper error propagation, meaningful tests, and disciplined debugging workflows. Always active when Claude writes or modifies code.
luoling8192/ai-coding-principles 145
obsidian Comprehensive guidelines for Obsidian.md plugin development including all 27 ESLint rules from eslint-plugin-obsidianmd v0.1.9, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, locale file sentence-case enforcement, and submission requirements. Use when working with Obsidian plugins, main.ts files, manifest.json, Plugin class, MarkdownView, TFile, vault operations, or any Obsidian API development.
gapmiss/obsidian-plugin-skill 119
Log Analyzer 智能日志分析工具，帮助快速定位应用错误和性能瓶颈
huifer/skill-security-scan 117
Data Optimizer Pro 智能数据优化工具，自动清理和优化项目文件
huifer/skill-security-scan 117
Log Analyzer 智能日志分析工具，帮助快速定位应用错误和性能瓶颈
huifer/skill-security-scan 117
harness-engineering-guide Audit, design, and implement AI agent harnesses for any codebase. A harness is the constraints, feedback loops, and verification systems surrounding AI coding agents — improving it is the highest-leverage way to improve AI code quality. Three modes: Audit (scorecard), Implement (set up components), Design (full strategy). Use whenever the user mentions harness engineering, agent guardrails, AI coding quality, AGENTS.md, CLAUDE.md setup, agent feedback loops, entropy management, AI code review, vibe coding quality, harness audit, harness score, AI slop, agent-first engineering. Also trigger when users want to understand why AI agents produce bad code, make their repo work better with AI agents, set up CI/CD for agent workflows, design verification systems, or scale AI-assisted development. Proactively suggest when discussing AI code drift or controlling AI-generated code quality.
OdradekAI/harness-engineering-guide 130
agile-scrum Use this skill when working with Agile and Scrum methodologies - sprint planning, retrospectives, velocity tracking, Kanban boards, story point estimation, backlog grooming, or team workflow optimization. Triggers on any task involving sprint ceremonies, agile metrics, user story writing, capacity planning, or continuous improvement processes.
AbsolutelySkilled/AbsolutelySkilled 116
absolute-ui Use this skill when building user interfaces that need to look polished, modern, and intentional - not like AI-generated slop. Triggers on UI design tasks including component styling, layout decisions, color choices, typography, spacing, responsive design, dark mode, accessibility, animations, landing pages, onboarding flows, data tables, navigation patterns, and any question about making a UI look professional. Covers CSS, Tailwind, and framework-agnostic design principles.
AbsolutelySkilled/AbsolutelySkilled 116
absolute-simplify Autonomously simplifies code in your working changes or targeted files. Detects staged or unstaged git changes, analyzes for simplification opportunities following clean code and clean architecture principles, applies improvements directly, runs tests to verify nothing broke, and shows a structured summary with reasoning. Triggers on "simplify this", "refactor this", "clean up my changes", "absolute-simplify", "simplify my code", "make this cleaner", "tidy this up", "reduce complexity", "flatten this", "remove dead code", or when code needs clarity improvements, nesting reduction, or redundancy removal. Language-agnostic at base with deep opinions for JS/TS/React, Python, and Go.
AbsolutelySkilled/AbsolutelySkilled 116