ReddRadar
Topic: codex
8,457 skills in this topic.
-
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
6BNBN/FlowPilot 127
-
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
6BNBN/FlowPilot 127
-
superpowers
Use when starting any conversation to discover relevant skills and open the right SKILL.md files before responding, including before clarifying questions.
6BNBN/FlowPilot 127
-
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
6BNBN/FlowPilot 127
-
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
6BNBN/FlowPilot 127
-
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
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
-
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 is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
6BNBN/FlowPilot 127
-
feature-dev
Use when the user asks to build a new feature and wants a structured Codex CLI workflow with discovery, clarifying questions, architecture comparison, implementation, and review.
6BNBN/FlowPilot 127
-
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
6BNBN/FlowPilot 127
-
code-quality
BA-CalderonMorales/terminal-jarvis 126
-
database
BA-CalderonMorales/terminal-jarvis 126
-
deployment
BA-CalderonMorales/terminal-jarvis 126
-
git-workflow
BA-CalderonMorales/terminal-jarvis 126
-
home-screen
BA-CalderonMorales/terminal-jarvis 126
-
homebrew
BA-CalderonMorales/terminal-jarvis 126
-
manual-patching
BA-CalderonMorales/terminal-jarvis 126
-
multi-repo
BA-CalderonMorales/terminal-jarvis 126
-
npm
BA-CalderonMorales/terminal-jarvis 126
-
qa-testing
BA-CalderonMorales/terminal-jarvis 126
-
refactoring
BA-CalderonMorales/terminal-jarvis 126
-
release
BA-CalderonMorales/terminal-jarvis 126
-
release-checklist
BA-CalderonMorales/terminal-jarvis 126