claude-next-level

Primary review entrypoint for plans, diffs, commits, subagent results, and pre-submit checks. Selects quick, standard, or deep mode by scale and risk.

Planner-led repo improvement loops with subagents, review gates, Mermaid DAGs, and workflow-aware commits. Use for improve, refactor, audit, or continue-loop requests.

Triage and apply code review feedback with technical verification. Use when a human, reviewer subagent, CI, or adversarial reviewer returns findings or requested changes.

Heavy review mode normally invoked by request-code-review for risky checkpoints, pre-submit stacks, OpenSpec/cflx acceptance, security-sensitive work, or explicit deep review, audit, or red-team requests.

Post-implementation cleanup for recent changes using parallel reuse, quality, and efficiency reviewers. Use after building a feature or fix, before commit, PR, or submit.

End-of-workflow learning loop for skill-guided work. Use at session/checkpoint closeout to classify GitHub/CodeRabbit/human/CI findings, log missed-review patterns, and propose skill improvements only when evidence justifies them.

Use this skill when working in a repo that uses Graphite (the `gt` CLI) for stacked PRs. Activates whenever the git common dir contains `.graphite_repo_config`, the project's CLAUDE.md mentions Graphite or `graphite-pr`, or the user mentions `gt`, stacked PRs, atomic commits, or splitting a change into reviewable pieces. Drives the daily commit → submit → review → merge loop and the rules for sizing atomic commits. To bootstrap Graphite in a new repo, read `references/setup.md` first.

Complete Jujutsu (jj) version control system for Git replacement. Use when migrating from Git, setting up colocated workspaces, managing commits without staging, working with bookmarks/branches, syncing with GitHub/remotes, resolving conflicts, or any jj command operations.

Domain knowledge for meta-orchestration — dispatch-and-poll patterns, wave coordination, merge-as-you-go, context management, JJ workspace integration, quality gate injection, cross-plugin routing, error recovery, wave planning algorithms, and orchestrator discipline. Core methodology for the chief-of-staff plugin.

Domain knowledge for meta-orchestration — dispatch-and-poll patterns, wave coordination, merge-as-you-go, JJ workspace integration, quality gate injection, cross-plugin routing, and error recovery. Core methodology for the chief-of-staff plugin.

Version control operations using Jujutsu (jj) — replaces git commit/push/PR workflows when `jj root` succeeds (i.e., inside a JJ workspace). Use when the user says "commit", "push", "create a PR", "describe", "bookmark", or any VC action in a JJ repo. Also use for jj-specific operations: revsets, stacked changes, conflict resolution, undo. If `jj root` succeeds, this skill takes priority over git workflows.

Use when porting code between languages, migrating a codebase, translating source code, or rewriting in a new language. Trigger phrases: "port", "clone to", "migrate to", "translate to", "rewrite in", "convert from X to Y".

Use for spec-driven development loops, porting code between languages, migrating codebases, retrospective analysis, or autonomous build loops. Trigger phrases: "ralph loop", "spec-driven", "build feature", "port", "clone to", "migrate to", "translate to", "rewrite in", "convert from X to Y", "autonomous loop", "implementation plan", "JTBD", "retrospective", "retro", "post-mortem", "what went wrong", "audit the project", "improvement todo".

Show current context usage, active spec status, project progress, omega memory state, and continuation info at a glance.

Health check for next-level — verifies config, dependencies, hooks, and state directories

Execute an epic — sequences tasks from GitHub issues, runs spec workflow per task, adversarial checkpoints between tasks.

Project-level planner — breaks large work into epics and tasks, creates GitHub issues with milestones, sequences execution order.

Quick implementation mode — skips plan phase, goes straight to TDD implementation with all quality hooks active.

Resume execution from a previous session — reads checkpoint state and continues where the last session left off.

Configure next-level for your project — detects languages, installs linters/formatters, writes config

Start or continue a spec-driven development workflow. Orchestrates plan → implement → verify cycle with approval gates.

Execute an epic using agent teams for parallel task execution. Team lead coordinates, coding agents implement, review agent checkpoints.

Use when the user wants to create a business offer, build a Grand Slam Offer, design pricing strategy, create an irresistible offer, or mentions Alex Hormozi, $100M Offers, value equation, offer creation, or offer workshop. Orchestrates a multi-phase workshop with adversarial agent teams that stress-test every decision.

Domain knowledge for multi-PR review orchestration — monitoring patterns, fix dispatch, worktree management, cross-PR intelligence, and CodeRabbit specifics. Referenced by /cycle:pr for batch PR operations.

Use when the user wants to build a lead generation system, create lead magnets, design outreach scripts, plan marketing channels, mentions Alex Hormozi, $100M Leads, Core Four, Rule of 100, warm outreach, cold outreach, lead magnets, customer acquisition, or lead generation strategy. Orchestrates a multi-phase workshop with adversarial agent teams that stress-test every decision.