Skill Claude CodeCodex
Manage a software project using 3 pattern languages: Business, Product, and Technical.
not rated 2 11d ago A 0 tokens
original MIT
code-review
02Skill Claude CodeCodex
Guidelines and checklist for rigorous, evidence-based code reviews covering correctness, tests, maintainability, cohesion, and architectural boundaries.
not rated 2
changed 11d ago A 28 tokens
original MIT
fix-bugs
03Skill Codex
Systematic bug-fixing workflow for reported defects, regressions, failing behavior, flaky tests, crashes, visual/UI bugs, platform-specific failures, stale or version-specific reports, log-reported errors, and production-like failures. Use when Codex is asked to investigate, debug, fix, or verify a bug and should…
not rated 2 11d ago A 109 tokens
original MIT
Skill Codex
Build, code-sign, install, and launch the current iOS app on a connected physical device. Use when the user asks to install, deploy, build and run, or put the current iOS project on their phone or iPad.
not rated 2
changed 2mo ago A 53 tokens
original MIT
Skill Claude CodeCodex
Manage a hierarchical Pattern Language for documenting abstract wisdom.
not rated 2 11d ago A 14 tokens
original MIT
Skill Claude CodeCodex
ALWAYS use this skill to access, address, reply to, or resolve GitHub PR review comments or Reviewable.io threads. Do NOT use raw gh pr comment, gh api, or any other gh subcommand directly — use the co-located reviewable script instead.
not rated 2 11d ago A 63 tokens
original MIT
review-plan
07Skill Claude CodeCodex
Guidelines and checklist for reviewing implementation plans consistently.
not rated 2
changed 11d ago A 13 tokens
original MIT
Skill Codex
Facilitate implementation-ready plans for new features using double-diamond discovery, BPT constraints, red/blue execution checkpoints, and fresh specialist briefback review. Use before implementation, not for executing an approved plan.
not rated 2
changed 1mo ago A 47 tokens
original MIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: