Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
seojaewan avatar

Try Claude

  • 1 repo stars
  • Updated July 28, 2026
  • SeoJaeWan/try-claude-code

try-claude-code is a Claude Code and Codex marketplace repository that bundles experimental develop and statusline plugins plus a Codex planning stack so teams can trial artifact-driven planning and review workflows.

About

try-claude is a marketplace bundling Claude Code execution plugins and a Codex planning stack used to test how rules split across plugins, skills, and review artifacts for stable reproduction with less context. Reach for it when you want to trial brainstorm-through-planning-docs loops, worktree-based development, and commit-level dev-review served from a local review server. It is described as a workflow workbench rather than a finished product, with outputs under plans/{task}/ when tasks run.

  • try-claude-code develop plugin: worktrees, hooks, stop-review gate, dev-review skills
  • Codex planning stack with artifact-driven orchestrator and plan-wiki integration
  • Local review UI at localhost:9797/review/{task} with commit-based dev-review

Try Claude by the numbers

  • Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin marketplace add SeoJaeWan/try-claude-code

Add your badge

Show developers this marketplace is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars1
Last updatedJuly 28, 2026
RepositorySeoJaeWan/try-claude-code

Which rules should live in plugins, skills, or review artifacts so assistants reproduce the same planning and implementation outcomes with smaller context windows?

Experiment with artifact-driven planning loops, worktree execution, dev-review gates, and a local multi-review server inside Claude Code and Codex stacks.

Who is it for?

Developers experimenting with Claude Code and Codex who want worktree execution, planning-doc gates, and localhost dev-review in one repo.

Skip if: Teams needing a stable, supported productized workflow without maintaining experimental plugins and plan-wiki clones.

What you get

Planning and dev-review artifacts land under plans/{task}/, with review HTML served locally and plan-wiki sources managed under .codex/plan-wiki per README.

Recommended Marketplaces

FAQ

What are the two Claude plugins?

README lists Try Claude-code at plugin/develop for execution and Try Claude-code-statusline at plugin/statusline for statusline controls.

Where do planning artifacts live?

Generated planning and review outputs are typically created under plans/{task}/ as task-specific artifacts.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.