Explore skills
Showing 28651–28680 of 77079 skills
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
stevesolun/ctx
Stars: 593Claude CodeCodexReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
stevesolun/ctx
Stars: 593Claude CodeCodexBreak a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
stevesolun/ctx
Stars: 593Claude CodeCodexTurn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
stevesolun/ctx
Stars: 593Claude CodeCodexShape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
stevesolun/ctx
Stars: 593Claude CodeCodexTake a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
stevesolun/ctx
Stars: 593Claude CodeCodexAlive skill router — reads the current project's stack and loads/unloads skills dynamically. Invoke at session start or when project context changes.
stevesolun/ctx
Stars: 593Claude CodeCodexPre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing toolboxes with a team.
stevesolun/ctx
Stars: 593Claude CodeCodexDetection engineering skill for writing, testing, and tuning Sigma, YARA, YARA-L, Suricata, Snort, Zeek, KQL, SPL, EQL, Chronicle, and Elastic detection rules. Covers ATT&CK coverage mapping, telemetry gap analysis, false-positive tuning, detection-as-code pipelines, and validation with Atomic Red Team and Caldera. Use to design durable detections backed by tests.
Garyson26/Trident-SecOps-Skills
Stars: 43Claude CodeCodexPrompt engineering and task-specification skill for improving prompts, agent instructions, system messages, evaluation prompts, coding-agent tasks, multi-step workflows, and LLM output reliability. Use when rewriting vague prompts, adding constraints, reducing ambiguity, improving safety, creating reusable prompt templates, or converting goals into actionable agent instructions.
Garyson26/Trident-SecOps-Skills
Stars: 43Claude CodeCodexUse when requirements exist and a technical design is needed before implementation begins
Trevoke/org-gtd.el
Stars: 487Claude CodeCodexUse when a new feature request, bug report, or work request needs requirements defined before implementation
Trevoke/org-gtd.el
Stars: 487Claude CodeCodexUse when a design exists and it's time to break it into tasks and execute with subagent dispatch and review
Trevoke/org-gtd.el
Stars: 487Claude CodeCodexUse when implementation is complete and you want to verify quality through adversarial testing that writes code and provides evidence
Trevoke/org-gtd.el
Stars: 487Claude CodeCodexUse when code quality needs improvement after implementation, without changing behavior
Trevoke/org-gtd.el
Stars: 487Claude CodeCodexUse when creating new skills, editing existing skills, or verifying skills work before deployment
Trevoke/org-gtd.el
Stars: 487Claude CodeCodexReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
ifelx74/nanoboard
Stars: 38Claude CodeCodexDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
ifelx74/nanoboard
Stars: 38Claude CodeCodexGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
ifelx74/nanoboard
Stars: 38Claude CodeCodexTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
ifelx74/nanoboard
Stars: 38Claude CodeCodexTurn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
ifelx74/nanoboard
Stars: 38Claude CodeCodexBreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
ifelx74/nanoboard
Stars: 38Claude CodeCodexUse when the user asks about dsh-tui itself (usage, shortcuts, config, themes, migration, VS Code). Load before answering; skip for normal coding tasks.
ccch1mneyyy/dsh-TUI
Stars: 7.8kClaude CodeCodexOpen a PR in this repo, end to end - find the real base branch (never assume main), split the working tree into one commit per feature, pull the Linear tickets, write a body that shows the change rather than describing it, and confirm the base, assignee and labels landed. Use whenever asked to make, open or push a PR, or to commit a working tree "by feature" so a PR can follow.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexWire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexPlan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexShip current branch — CI, SonarCloud, code review, security review, fix all issues, merge. Assumes code is already committed and pushed.
PaloAltoNetworks/shifter
Stars: 7Claude CodeCodexBackground memory consolidation — overnight review, merge, and injection payload for memory files.
notque/vexjoy-agent
Stars: 451Claude CodeCodexAdvisor mode: audit a codebase, rank what is worth doing, and write self-contained handoff plans that a fresh agent executes. Never edits source itself. Use for "what should we improve", "find improvement opportunities", "what to build next", "write a plan another agent can run", "execute plan 003", or "reconcile the plans".
notque/vexjoy-agent
Stars: 451Claude CodeCodexUniversal radial-tree exploration engine — loads a preset, grounds a root, expands every node through 12 framing passes, derives each child in 12 evidence-bearing fields, scores it, and recurses on `advances` leaves until substantive convergence (or a user cap). Caps default to ∞; `defer / TODO / NEEDS-MORE-INFO` leaves are hard-banned. Use when the user wants the engine itself — a custom preset via `--preset <path>`, explicit control of a run, or "tree of thoughts" / 穷尽的树状探索 in general; for the four shipped use-cases prefer `/cc-tree:brainstorm`, `/cc-tree:attack`, `/cc-tree:design`, `/cc-tree:code-audit`, whose descriptions carry the per-use-case triggers.
skymanbp/cc-tree
Stars: 80Claude CodeCodex