cli-reference

parcadei/continuous-claude-v3 · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill cli-reference
0 commentsdiscussion
summary

Complete reference for Claude Code command-line interface.

skill.md

CLI Reference

Complete reference for Claude Code command-line interface.

When to Use

  • "What CLI flags are available?"
  • "How do I use headless mode?"
  • "Claude in automation/CI/CD"
  • "Output format options"
  • "System prompt via CLI"
  • "How do I spawn agents properly?"

Core Commands

Command Description Example
claude Start interactive REPL claude
claude "query" REPL with initial prompt claude "explain this project"
claude -p "query" Headless mode (SDK) claude -p "explain function"
cat file | claude -p Process piped content cat logs.txt | claude -p "explain"
claude -c Continue most recent claude -c
claude -c -p "query" Continue via SDK claude -c -p "check types"
claude -r "id" "query" Resume session claude -r "auth" "finish PR"
claude update Update version claude update
claude mcp Configure MCP servers See MCP docs

Session Control

Flag Description Example
--continue, -c Load most recent conversation claude --continue
--resume, -r Resume session by ID/name claude --resume auth-refactor
--session-id Use specific UUID claude --session-id "550e8400-..."
--fork-session Create new session on resume claude --resume abc --fork-session

Headless Mode (Critical for Agents)

Flag Description Example
--print, -p Non-interactive, exit after claude -p "query"
--output-format text, json, stream-json claude -p --output-format json
--max-turns Limit agentic turns claude -p --max-turns 100 "query"
--verbose Full turn-by-turn output claude --verbose
--dangerously-skip-permissions Skip permission prompts claude -p --dangerously-skip-permissions
--include-partial-messages Include streaming events claude -p --output-format stream-json --include-partial-messages
--input-format Input format (text/stream-json) claude -p --input-format stream-json

Tool Control

Flag Description Example
--allowedTools Auto-approve these tools "Bash(git log:*)" "Read"
--disallowedTools Block these tools "Bash(rm:*)" "Edit"
--tools Only allow these tools --tools "Bash,Edit,Read"

Subagent Definition (--agents flag)

Define custom subagents inline via JSON:

claude --agents '{
  "code-reviewer": {
    "description": "Expert code reviewer. Use proactively after code changes.",
    "prompt": "You are a senior code reviewer. Focus on code quality and security.",
    "tools": ["Read", "Grep", "Glob", "Bash"],
    "model": "sonnet"
  },
  "debugger": {
    "description": "Debugging specialist for errors and test failures.",
    "prompt": "You are an expert debugger. Analyze errors and provide fixes."
  }
}'

Agent Fields

Field Required Description
description Yes When to invoke this agent
prompt Yes System prompt for behavior
tools No Allowed tools (inherits all if omitted)
model No sonnet, haiku, or claude-opus-4-5-20251101

Key Insight

When Lead uses Task tool, it auto-spawns from these definitions. No manual spawn needed.

System Prompt Customization

Flag Behavior Modes
--system-prompt Replace entire prompt Interactive + Print
--system-prompt-file Replace from file Print only
--append-system-prompt Append to default (recommended) Interactive + Print

Use --append-system-prompt for most cases - preserves Claude Code capabilities.

Model Selection

Flag Description Example
--model Set model for session --model claude-sonnet-4-5
--fallback-model Fallback if default overloaded --fallback-model sonnet

Aliases: sonnet, opus, haiku

MCP Configuration

Flag Description Example
--mcp-config Load MCP servers from JSON --mcp-config ./mcp.json
--strict-mcp-config Only use these MCP servers --strict-mcp-config --mcp-config ./mcp.json

Advanced Flags

Flag Description Example
--add-dir Add working directories --add-dir ../apps ../lib
--agent Specify agent for session --agent my-custom-agent
--permission-mode Start in permission mode --permission-mode plan
--permission-prompt-tool MCP tool for permissions --permission-prompt-tool mcp_auth
--plugin-dir Load plugins from directory --plugin-dir ./my-plugins
--settings Load settings from file/JSON --settings ./settings.json
--setting-sources Which settings to load --setting-sources user,project
--betas Beta API headers --betas interleaved-thinking
--debug Enable debug mode --debug "api,hooks"
--ide Auto-connect to IDE --ide
--chrome Enable Chrome integration --chrome
--no-chrome Disable Chrome for session --no-chrome
--enable-lsp-logging Verbose LSP debugging --enable-lsp-logging
--version, -v Output version claude -v

Output Formats

JSON (for parsing)

claude -p "query" --output-format json
# {"result": "...", "session_id": "...", "usage": {...}}

Streaming (for real-time monitoring)

claude -p "query" --output-format stream-json
# Newline-delimited JSON events

Structured Output (schema validation)

claude -p "Extract data" \
  --output-format json \
  --json-schema '{"type":"object","properties":{...}}'

Headless Agent Pattern (CRITICAL)

Proper headless agent spawn:

claude -p "$TASK_PROMPT" \
  --session-id "$UUID" \
  --dangerously-skip-permissions \
  --max-turns 100 \
  --output-format stream-json \
  --agents '{...}' \
  --append-system-prompt "Context: ..."

Missing any of these causes hangs:

  • --session-id - Track the session
  • --dangerously-skip-permissions - Headless requires this
  • --max-turns - Prevents infinite loops

Common Patterns

CI/CD Automation

claude -p "Run tests and fix failures" \
  --dangerously-skip-permissions \
  --max-turns 50 \
  --output-format json | jq '.result'

Piped Input

cat error.log | claude -p "Find root cause"
gh pr diff | claude -p "Review for security"

Multi-turn Session

id=$(claude -p "Start task" --output-format json | jq -r '.session_id')
claude -p "Continue" --resume "$id"

Stream Monitoring

claude -p "Long task" \
  --output-format stream-json \
  --include-partial-messages | while read -r line; do
    echo "$line" | jq '.type'
done

Keyboard Shortcuts (Interactive)

Shortcut Action
Ctrl+C Cancel current
Ctrl+D Exit
Ctrl+R Reverse search history
Esc Esc Rewind changes
Shift+Tab Toggle permission mode

Quick Commands

Prefix Action
/ Slash command
! Bash mode
# Add to memory
@ File mention
how to use cli-reference

How to use cli-reference on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add cli-reference
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill cli-reference

The skills CLI fetches cli-reference from GitHub repository parcadei/continuous-claude-v3 and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/cli-reference

Reload or restart Cursor to activate cli-reference. Access the skill through slash commands (e.g., /cli-reference) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.846 reviews
  • Isabella Jackson· Dec 24, 2024

    Registry listing for cli-reference matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Isabella Liu· Dec 20, 2024

    Useful defaults in cli-reference — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Dhruvi Jain· Dec 16, 2024

    Solid pick for teams standardizing on skills: cli-reference is focused, and the summary matches what you get after install.

  • Kwame Brown· Dec 8, 2024

    I recommend cli-reference for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Isabella Zhang· Nov 27, 2024

    cli-reference reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Omar Taylor· Nov 23, 2024

    cli-reference is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Lucas Thompson· Nov 15, 2024

    Useful defaults in cli-reference — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Min Menon· Nov 11, 2024

    Registry listing for cli-reference matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Oshnikdeep· Nov 7, 2024

    We added cli-reference from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ganesh Mohane· Oct 26, 2024

    cli-reference fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 46

1 / 5