Complete reference for Claude Code command-line interface.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncli-referenceExecute the skills CLI command in your project's root directory to begin installation:
Fetches cli-reference from parcadei/continuous-claude-v3 and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate cli-reference. Access via /cli-reference in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
3.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3.7K
stars
Complete reference for Claude Code command-line interface.
| 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 |
| 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 |
| 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 |
| 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" |
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."
}
}'
| 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 |
When Lead uses Task tool, it auto-spawns from these definitions. No manual spawn needed.
| 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.
| 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
| 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 |
| 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 |
claude -p "query" --output-format json
# {"result": "...", "session_id": "...", "usage": {...}}
claude -p "query" --output-format stream-json
# Newline-delimited JSON events
claude -p "Extract data" \
--output-format json \
--json-schema '{"type":"object","properties":{...}}'
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 loopsclaude -p "Run tests and fix failures" \
--dangerously-skip-permissions \
--max-turns 50 \
--output-format json | jq '.result'
cat error.log | claude -p "Find root cause"
gh pr diff | claude -p "Review for security"
id=$(claude -p "Start task" --output-format json | jq -r '.session_id')
claude -p "Continue" --resume "$id"
claude -p "Long task" \
--output-format stream-json \
--include-partial-messages | while read -r line; do
echo "$line" | jq '.type'
done
| Shortcut | Action |
|---|---|
Ctrl+C |
Cancel current |
Ctrl+D |
Exit |
Ctrl+R |
Reverse search history |
Esc Esc |
Rewind changes |
Shift+Tab |
Toggle permission mode |
| Prefix | Action |
|---|---|
/ |
Slash command |
! |
Bash mode |
# |
Add to memory |
@ |
File mention |
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
parcadei/continuous-claude-v3
mattpocock/skills
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for cli-reference matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in cli-reference — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: cli-reference is focused, and the summary matches what you get after install.
I recommend cli-reference for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
cli-reference reduced setup friction for our internal harness; good balance of opinion and flexibility.
cli-reference is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in cli-reference — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for cli-reference matched our evaluation — installs cleanly and behaves as described in the markdown.
We added cli-reference from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
cli-reference fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 46