ReddRadar
Topic: codex
8,457 skills in this topic.
-
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 commit seed.
sd0xdev/sd0x-dev-flow 139
-
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
-
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
-
install-scripts
Install plugin runner scripts into project .claude/scripts/ for persistent use without plugin loaded
sd0xdev/sd0x-dev-flow 139
-
desloppify
verseles/codewalk 140
-
code-review
Use when the user asks for a code review of local files, a workspace, a branch diff, or a pull request. Focus on real bugs, regressions, accessibility issues, and misleading behavior, with findings ordered by severity.
6BNBN/FlowPilot 127
-
writing-skills
Use when creating, editing, or validating Cursor custom skills, especially when deciding where they should live, how they should be named, and how to describe when they apply.
6BNBN/FlowPilot 127
-
writing-plans
Use when the user wants a written implementation plan in Cursor before editing code, especially for multi-step tasks or changes touching several files.
6BNBN/FlowPilot 127
-
verification-before-completion
Use before claiming work is complete, fixed, or passing in Cursor. Requires fresh verification evidence such as tests, builds, lint output, or direct reproduction checks.
6BNBN/FlowPilot 127
-
using-git-worktrees
Use when starting feature work that should be isolated from the current checkout, especially in git repositories where a separate worktree would reduce risk.
6BNBN/FlowPilot 127
-
systematic-debugging
Use when diagnosing a bug, failing test, build issue, or unexpected behavior in Cursor before proposing a fix. Focus on reproducing the issue, tracing the cause, and validating the repair.
6BNBN/FlowPilot 127
-
subagent-driven-development
Use when executing a larger plan in Cursor with parallel or delegated work, while keeping tasks narrowly scoped and reviewed between steps.
6BNBN/FlowPilot 127
-
receiving-code-review
Use when acting on code review feedback in Cursor, especially if suggestions seem unclear, debatable, or risky. Helps evaluate feedback technically before changing code.
6BNBN/FlowPilot 127
-
playwright
6BNBN/FlowPilot 127
-
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
6BNBN/FlowPilot 127
-
finishing-a-development-branch
Use when implementation work is done and you need to decide how to finish it in Cursor, such as keeping the branch, merging locally, creating a pull request, or cleaning up temporary workspaces.
6BNBN/FlowPilot 127
-
feature-dev
Use when building a new feature or substantial behavior change in Cursor and the user wants a structured workflow from discovery through implementation and review.
6BNBN/FlowPilot 127
-
executing-plans
Use when a written implementation plan already exists in Cursor and the next step is to execute it in small batches with checkpoints and verification.
6BNBN/FlowPilot 127
-
dispatching-parallel-agents
Use when facing two or more independent tasks in Cursor that can be investigated or executed in parallel without conflicting edits or shared state.
6BNBN/FlowPilot 127
-
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
6BNBN/FlowPilot 127
-
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
6BNBN/FlowPilot 127
-
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
6BNBN/FlowPilot 127