jckeen
UserOne-command jumpstart for Claude Code + Codex on macOS and Windows (WSL2). 11 slash commands, 16-agent review orchestra, 4 safety hooks, multi-session tooling, status line, auto-hygiene — opinionated defaults so you don't have to remember the setup.
Categories
Indexed Skills (15)
fix-issue
Pick up a GitHub issue, investigate, implement the fix, test, and create a PR
branch-hygiene
Inspect and clean stale branches across multiple repositories using the dotfiles git-hygiene + gh-bootstrap toolchain. Use when the user asks about branch state, stale local branches, or "no ref was fetched" errors.
decompose
Deep task decomposition into parallel workstreams with self-contained agent prompts. Use when you want to review the execution plan before committing to it.
jj
Drives jujutsu (jj) version control on the user's behalf so they don't have to memorize commands. Use for single-agent feature work (the default), whenever the user mentions jujutsu/jj, when undo-safety or a clean rewritable history matters, or when starting/finishing a change in a jj-managed repo. For MULTI-agent parallel work use git worktrees (or jj workspaces) instead — see "jj vs worktrees" below.
max
Maximum effort mode — worktrees, parallel agents, batches, full capability selection. Use when you want comprehensive, no-compromise execution.
session-retro
Runs a short retrospective that PROPOSES edits to the user's Claude Code skills — capturing a newly-found gotcha, fixing a description that didn't auto-trigger, retiring a dead skill, or extracting a reusable pattern into a new skill. Improves the TOOLSET, not the session log. Use when the user signals satisfaction at the end of real work ("thanks", "thanks that worked", "that worked great", "nice", "perfect", "exactly what I needed"), or when they explicitly run /session-retro. Always proposes and waits for confirmation — never edits skills silently. In unattended runs (/max, overnight, or /session-retro --auto), writes proposals to ~/.claude/retro-proposals/ instead of blocking.
commit-push-pr
Commit current work, push the branch, and create a GitHub pull request with a concise title, body, and verification notes.
changelog
Update a project CHANGELOG.md or equivalent session log with concise notes about completed changes, decisions, and known issues.
claude-server
Starts a Claude Code remote-control server via `claude remote-control --spawn worktree`, running in an isolated git worktree so remote work doesn't touch local changes, and returns the connection info for claude.ai/code and the Claude mobile app. Use when the user wants to control this project remotely, asks to "start the remote server", "connect from my phone/mobile", "access this from claude.ai", or "spin up claude-server".
handoff
Generate a concise session handoff for resuming work later, including current state, decisions, open issues, and next steps.
kickoff
Scaffolds a new project in the current directory — creates CLAUDE.md, CHANGELOG.md, .gitignore, README.md, and a source dir, initializes git with a first commit, and offers to create a GitHub repo. Prompts for project name, description, and language/framework first. Use when the user wants to "start a new project", "bootstrap a repo", "set up a fresh project", "scaffold a codebase", or "kick off" a new build from scratch.
log-error
Records a recurring failure into ERRORS.md — classifies it (hallucination, instruction-ignored, context-lost, wrong-tool, incomplete, external), captures the goal, exact error, attempts tried, root cause, and lesson, then commits it; also logs wins on request. Use when the same error keeps recurring, an approach repeatedly fails, the user says "log this error", "document this failure", "this keeps happening", or "log that as a win" after a success.
review
Review recent or specified code changes for correctness, security, quality, and missing verification. Use when the user asks for a review, pre-ship check, PR review, or quality/security pass.
simplify
Review and simplify recently changed code by removing unnecessary complexity without changing behavior. Use when the user asks to simplify, reduce over-engineering, clean up a patch, or make code easier to maintain.
repo-health
Produce a read-only repository health briefing covering stack, git state, setup, tests, dependencies, blockers, and next steps.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.