Topic: codex
8,457 skills in this topic.
-
install-hooks
Install plugin hooks into project .claude/ for persistent use without plugin loaded
sd0xdev/sd0x-dev-flow 139
-
codex-test-review
Review test case sufficiency using Codex MCP, suggest additional edge cases. Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
-
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
sd0xdev/sd0x-dev-flow 139
-
codex-test-gen
Generate unit tests for specified functions using Codex MCP
sd0xdev/sd0x-dev-flow 139
-
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.
sd0xdev/sd0x-dev-flow 139
-
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.
sd0xdev/sd0x-dev-flow 139
-
desloppify
verseles/codewalk 140
-
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
-
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
-
playwright
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
6BNBN/FlowPilot 127
-
superpowers
Use when a task in Cursor may benefit from a structured workflow and one or more companion skills from this pack, such as brainstorming, feature development, design, review, debugging, planning, or verification.
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