Skip to main content
command CX Codex

default · serpro69, review-spec — Claude Code command: what it does, how to install

default validates code against feature design files to catch spec deviations, missing requirements, and outdated docs.

Elastic-2.0 ★ 155 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add serpro69/claude-toolbox
/plugin install kk@claude-toolbox
Open on GitHub

What default does

The command inspects code using documents located in /docs/feat/wip/<feature>/. It triggers the kk:review-spec skill and executes the sequence from review-process.md. Three specification files must exist: design.md, implementation.md, and tasks.md.

First, the process determines the review scope. Then it audits each task individually against the documentation and checks cross-cutting concerns. Next, the assistant rates its confidence on a 1 to 10 scale with rationale. A summary of findings follows with suggested next actions.

Without the expected /docs/feat/wip/ folder layout, the verification will fail. If you omit the feature argument, the command lists available WIP items or automatically selects the only one present.

What it helps with

  • spot differences between actual code and design.md
  • detect unaddressed requirements from tasks.md
  • identify outdated documentation after code changes
  • calculate an implementation confidence rating from 1 to 10

Example prompts for the agent

  • /kk:review-spec jwt-auth
  • /kk:review-spec

How to install default

1Plugin marketplace

/plugin marketplace add serpro69/claude-toolbox
/plugin install kk@claude-toolbox

2Manually: put the files in place

.claude/commands/default.md

Call it with /default. For all projects use ~/.claude/commands/

Questions about default

How to install default in Claude Code?

First, register the catalog source with /plugin marketplace add serpro69/claude-toolbox. Then run /plugin install kk@claude-toolbox to complete the installation.

What does the default command do?

It cross-references your source code with feature design files, checks every task, and gives a confidence score from 1 to 10.

Which files are required for the review?

The target folder under /docs/feat/wip/ must contain design.md, implementation.md, and tasks.md.

Similar slash commands

All slash commands for Code review and refactoring →

default by other authors comes first.

default serpro69 The default command checks an answer with Chain-of-Verification: it creates fact-checking questions, answers them separately, then revises the result. CX Codex +1 ★ 155repo stars code-to-spec smallnest code-to-spec reads an existing project and rebuilds a SPEC document from its code, config and tests. Useful when there is no spec and you still need to understand the thing. CX Codex +1 491installs architecture-review owainlewis architecture-review — a skill for Claude Code and Codex reviews RFCs, ADRs, and technical proposals before code gets written. It flags critical architectural flaws, unsafe patterns, and missing recovery paths. CX Codex +1 347installs spec-writer dannwaneri spec-writer transforms a vague feature request into a structured specification, technical plan, and task breakdown. Every assumption is marked inline so you can correct it before handing off to an agent. CX Codex +1 ★ 29repo stars weed juxt weed compares .allium specifications with implementation code, finds where they diverged and helps resolve it. Useful when spec and code have drifted apart. CX Codex +1 2,700installs review JuliusBrussee Runs an adversarial senior review of the spec before any code is written. Builds a skeptic and tries to refute the plan instead of rubber-stamping it. CX Codex +1 811installs verify kirkchen verify is a Claude Code skill that checks an implementation against change artifacts before archiving. It supports independent verification and reruns after fixes. CX Codex +1 526installs

From the same set30

The whole set →
greet Returns a one-line greeting that addresses the user by name in the language they pick. Falls back to English when no language is given. CX Codex +1 ★ 155repo stars example-skill example-skill is a Claude Code skill that validates input data and builds a conformance report. It runs during diff-skill evaluation tests. CX Codex +1 ★ 155repo stars default The default command checks an answer with Chain-of-Verification: it creates fact-checking questions, answers them separately, then revises the result. CX Codex +1 ★ 155repo stars review-tool The review-tool skill checks tool configuration files against project schemas and reports violations. Use it when you need a full scan that continues after errors appear. CX Codex +1 ★ 155repo stars merge-docs merge-docs combines two doc sets for one feature into one: design, plan and tasks. Handy when design ran twice and you need a single version to build from. CX Codex +1 ★ 155repo stars isolated isolated — a command that runs code review through a separate spec-reviewer sub-agent with no authorship bias. Surfaces gaps between documentation and implementation by comparing them from scratch. CX Codex +1 ★ 155repo stars isolated The command checks an answer by assigning separate verification questions to isolated sub-agents. Use it to review factual claims or investigate code in a project. CX Codex +1 ★ 155repo stars diff-skill Diffs two revisions of a skill's markdown instructions and flags the edits that weaken a rule or add avoidable complexity. Useful before you accept changes to a skill you rely on. CX Codex +1 ★ 155repo stars

Project sponsors

Companies that keep this analytics open