Built-in Capabilities Overview

Overview of built-in slash commands, Subagents, Skills, and Workflows in Qoder CLI

Qoder CLI comes with a comprehensive set of out-of-the-box capabilities upon installation, requiring no additional configuration to use. These built-in capabilities fall into four categories:

• Slash commands: Commands entered in the interactive interface starting with /, used to manage sessions, configurations, extensions, and workflows.
• Built-in Subagents: Dedicated subagents pre-configured in Qoder CLI, responsible for specific tasks such as code exploration, planning, memory management, status bar configuration, and usage Q&A.
• Built-in Skills: Pre-configured reusable skills that encapsulate common workflows (code review, debugging, security review, loop execution, etc.) into directly callable capabilities.
• Workflows: Orchestrate multi-step tasks into repeatable processes.

This page provides an overview and navigation for these four categories. For detailed parameters, aliases, scopes, and other specifics, see Built-in Agent and Skills Reference and Slash Commands Reference.

Built-in Slash Commands

In the interactive interface, typing / brings up the command list with fuzzy matching support. Slash commands allow you to directly execute management and auxiliary operations within a session without leaving the current conversation. They are broadly grouped by purpose as follows.

Session Management

Command	Purpose
/new	Create a new empty session.
/clear	Clear the screen and conversation history to start a new session (similar to /new).
/continue	Resume the previous session.
/resume	Select and restore a session from the historical session list.
/rename	Rename the current session.
/rewind	Roll back to a previous checkpoint to restore code or conversation state.
/export	Export the current session content.
/compact	Compact the current conversation context to free up space in the context window.
/quit	Exit Qoder CLI.

For complete details on session management, see Session Management and Rewind Changes and Restore Sessions.

Configuration and Account

Command	Purpose
/login	Sign in and complete authentication.
/logout	Sign out of the current account.
/model	Select or switch models.
/theme	Switch the UI Theme.
/editor	Configure the external editor.
/settings	View and adjust settings.
/init	Initialize project configuration (generate project instructions file, etc.).
/profile	View User Profile.
/privacy	View and adjust privacy settings.
/permissions	Manage permissions (view and adjust permission rules).
/vim	Toggle Vim edit mode.
/voice	Enable Voice Input.
/statusline	Configure Custom Status Bar.

For configuration hierarchy and application order, see Configuration Files and Application Order.

Extensions and Tools

Command	Purpose
/agents	Manage Subagents (create, edit, view).
/skills	Manage Skills.
/mcp	Manage configured MCP Servers.
/hooks	Manage Hooks.
/plugins	Manage plugins.
/marketplace	Browse and install extensions.
/tools	View available Built-in Tools.

For detailed usage of each extension mechanism, see Subagent, Skills, MCP, Hooks, and Plugins.

Workflows and Tasks

Command	Purpose
/plan	Enter Plan mode (plan first, then execute).
/tasks	Manage Tasks.
/workflows	Manage Workflows.
/kanban	View tasks in Kanban View.
/review	Review Changes.
/diff	View diffs.

Information and Usage

Command	Purpose
/help	View help.
/docs	Open documentation.
/shortcuts	View keyboard shortcuts.
/usage	View Usage and Quotas.
/insights	View sessions and Usage Insights.
/status	View current status.
/context	View context composition.
/release-notes	View Release Notes.
/feedback	Submit feedback.
/about	About Qoder CLI.

Command Availability

Some built-in commands are dynamically shown or hidden based on the current environment and settings:

• Dependent on Feature Flags: Commands such as Subagent, Plan mode, Skills, Workflows, and extension marketplace only appear when the corresponding capabilities are enabled.
• Disabled by Settings: For example, when MCP is disabled via settings, /mcp will prompt “MCP has been disabled by settings”; when Skills are turned off by a Management Policy, /skills will prompt that they are disabled.
• Version Differences: Some commands are only available in specific Release Versions or on specific platforms.
• Debug Only: Some commands are only visible in development or Debug Mode and do not appear during normal usage.

If you do not see a certain command, it usually means the corresponding capability is not yet enabled or has been turned off via settings. For the complete list, aliases, and scopes of slash commands, see Slash Commands Reference.

Built-in Subagents

Subagents are specialized agents with independent context, dedicated prompts, and toolsets. Qoder CLI comes with several built-in Subagents pre-configured, covering scenarios such as exploration, planning, memory management, and Q&A. They are automatically delegated by the main session when needed, and can also be explicitly specified in supported scenarios.

Subagent	Purpose	Characteristics
general-purpose	A general-purpose research subagent, suitable for complex searches, multi-file analysis, call chain tracing, and multi-step tasks.	Default subagent, can use all tools (except main session-specific tools).
Explore	Fast read-only code exploration: find files by pattern, search keywords, and understand existing implementations.	Read-only, disables write and state-changing tools; the thoroughness of exploration (quick / medium / very thorough) can be specified when called.
Plan	Read-only plan design: sort out implementation paths, key files, dependency order, and architectural trade-offs.	Read-only, outputs a step-by-step implementation plan and lists key files.
memory-manager	Manages cross-session memory, preferences, and facts, maintaining personal-level and project-level instructions files.	Only available when the memory management capability is enabled; only reads and writes memory files.
statusline-setup	Configures Custom Status Bar: reads Shell configuration, generates scripts, and updates settings.	Only available in the interactive interface.
qoder-guide	Answers questions about Qoder CLI usage, configuration, Skills, Subagents, MCP, and Hooks.	Prioritizes answering based on official documentation; only available in the interactive interface.

Built-in Subagents can be used without manual creation. You can also create your own Subagents based on these; see Subagent. For details on the toolsets, models, and invocation methods of each built-in Subagent, see Built-in Agent and Skills Reference.

Built-in Skills

Skills encapsulate common workflows into reusable capabilities. Built-in Skills are provided with Qoder CLI and can be invoked directly as slash commands (e.g., /simplify). Some are also automatically triggered by the model in appropriate scenarios.

Skill	Purpose
/simplify	Reviews changed code for reusability, quality, and efficiency issues, and launches multiple review perspectives in parallel to fix discovered issues.
/debug	Enables debug logs for the current session, reads the tail of the log, and assists in diagnosing issues.
/security-scan	Executes a Qoder cloud security scan on the entire repository or specified paths, supporting L2 Lightweight and L3 Deep Review.
/quest	An intelligent workflow orchestrator that guides you through feature development step-by-step using dedicated subagents.
/mcp-config	Interactively adds, updates, or removes MCP Server configurations.
/loop	Repeatedly runs a prompt or slash command at fixed intervals.
/run	Starts and drives the project’s actual application to observe the effects of changes at runtime.
/verify	Verifies whether code changes achieve the expected results by running the application and observing its behavior.
/remember	Reviews Auto-Memory entries, suggests promotions to instructions files, and identifies outdated, conflicting, and duplicate entries.
/batch	Applies bulk changes across multiple files by generating parallel working agents in isolated git worktrees.
/run-skill-generator	Generates a project-level skill for the project’s run and debug steps.

Trigger Methods

Built-in Skills have two trigger methods:

• Manual Invocation: Enter the corresponding slash command in the interactive interface (e.g., /security-scan).
• Automatic Trigger: Some Skills are automatically used when the model deems it appropriate. Conversely, Skills marked as not automatically triggered, such as /debug, /security-scan, and /batch, are only executed when explicitly called.

Conditional Enablement

Some built-in Skills depend on specific prerequisites:

• /batch requires the worktree isolation capability to be enabled (and the current directory must be a Git repository).
• /remember requires the Auto-Memory capability to be enabled.

When prerequisites are not met, these Skills will not appear in the available list. For complete parameters and behaviors of built-in Skills, see Built-in Agent and Skills Reference; to learn how to write your own Skills, see Skills.

Workflows

Workflows orchestrate a series of steps into repeatable processes, making them ideal for standardizing recurring multi-step tasks within a team. You can use /workflows to manage workflows, and /tasks and /kanban to track task progress. For detailed usage of workflows, see Workflows.

How to Choose

• Need to perform one-off management or auxiliary operations in a session → Use slash commands.
• Need to delegate a category of tasks requiring independent context and dedicated standards to a focused executor → Use Subagents.
• Need to reuse a mature workflow (code review, debugging, security review, loop execution, etc.) → Use Skills.
• Need to standardize multi-step tasks into repeatable processes → Use Workflows.

Next Steps

• Consult command details: Slash Commands Reference, Built-in Agent and Skills Reference.
• Extend capabilities: Subagent, Skills, Plugins.
• Integrate team knowledge: Knowledge Base.