An overview of Qoder CLI CN's built-in slash commands, Subagents, Skills, and workflows
Qoder CLI CN ships with a full set of ready-to-use capabilities out of the box, no extra configuration required. These built-in capabilities fall into four categories:
In the interactive interface, typing
For the full description of session management, see Managing Sessions and Undo and Restore.
For configuration layers and precedence, see Settings Files and Precedence.
For detailed usage of each extension mechanism, see the sections below and MCP Reference, Hooks Reference, and Plugins Reference.
Some built-in commands are shown or hidden dynamically based on the current environment and settings:
A Subagent is a subordinate agent with its own context, dedicated prompt, and tool set. Qoder CLI CN comes with several built-in Subagents covering exploration, planning, memory, and Q&A. They are delegated automatically by the main session when needed, and can also be specified explicitly where supported.
Built-in Subagents work without manual creation, and you can create your own Subagents with the
Skills package common workflows into reusable capabilities. Built-in Skills ship with Qoder CLI CN and can be invoked directly as slash commands (for example
Built-in Skills trigger in two ways:
A few built-in Skills depend on specific prerequisites:
Workflows orchestrate a series of steps into a repeatable process, ideal for solidifying multi-step tasks that recur within a team. Use
- Slash Commands: commands typed with a leading
/in the interactive interface, for managing sessions, configuration, extensions, and workflows. - Built-in Subagents: dedicated subagents preloaded with Qoder CLI CN, handling specific tasks such as code exploration, solution design, memory management, status line configuration, and usage Q&A.
- Built-in Skills: preloaded reusable skills that package common workflows (review, debugging, security review, looped execution, and more) into directly invocable capabilities.
- Workflows: orchestrate multi-step tasks into repeatable processes.
Built-in slash commands
In the interactive interface, typing / pops up the command list with fuzzy matching. Slash commands let you perform management and auxiliary operations directly within the session without leaving the conversation. By purpose they roughly group as follows.
Session management
| Command | Purpose |
|---|---|
/new | Start a new empty session. |
/clear | Clear the screen and conversation history, starting a new session (similar to /new). |
/continue | Continue the previous session. |
/resume | Pick and resume a session from the history list. |
/rename | Rename the current session. |
/rewind | Rewind to an earlier checkpoint, restoring code or conversation state. |
/export | Export the current session content. |
/compact | Compress the current conversation context to free context window space. |
/quit | Exit Qoder CLI CN. |
Configuration and account
| Command | Purpose |
|---|---|
/login | Sign in and complete authentication. |
/logout | Sign out of the current account. |
/model | Select or switch the model. |
/theme | Switch the interface theme. |
/editor | Configure the external editor. |
/settings | View and adjust settings. |
/init | Initialize project configuration (generate the project instructions file, etc.). |
/profile | View the user profile. |
/privacy | View and adjust privacy-related settings. |
/permissions | Manage permissions (view and adjust permission rules). |
/vim | Toggle Vim editing mode. |
/voice | Enable voice input. |
/statusline | Configure a custom status line. |
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 the available built-in tools. |
Workflows and tasks
| Command | Purpose |
|---|---|
/plan | Enter Plan (plan before executing) mode. |
/tasks | Manage tasks. |
/workflows | Manage workflows. |
/kanban | View tasks in a kanban view. |
/review | Review code changes. |
/diff | View diffs. |
Information and usage
| Command | Purpose |
|---|---|
/help | View help. |
/docs | Open the documentation. |
/shortcuts | View keyboard shortcuts. |
/usage | Check usage and quota. |
/insights | View session and usage insights. |
/status | View the current status. |
/context | View the context composition. |
/release-notes | View release notes. |
/feedback | Submit feedback. |
/about | About Qoder CLI CN. |
Command availability
Some built-in commands are shown or hidden dynamically based on the current environment and settings:
- Feature-gated: commands such as Subagent, Plan mode, Skills, workflows, and the extensions marketplace only appear when the corresponding capability is enabled.
- Disabled by settings: for example, when MCP is disabled by settings,
/mcpreports "MCP is disabled by settings"; when Skills is turned off by an admin policy,/skillsreports it is disabled. - Varies by release: some commands are only available in certain releases or platforms.
- Debug-only: some commands are visible only in development or debug mode and do not appear in normal use.
Built-in Subagents
A Subagent is a subordinate agent with its own context, dedicated prompt, and tool set. Qoder CLI CN comes with several built-in Subagents covering exploration, planning, memory, and Q&A. They are delegated automatically by the main session when needed, and can also be specified explicitly where supported.
| Subagent | Purpose | Characteristics |
|---|---|---|
| general-purpose | General research subagent for complex searches, multi-file analysis, call-chain tracing, and multi-step tasks. | The default subagent; can use all tools (except tools exclusive to the main session). |
| Explore | Fast read-only code exploration: find files by pattern, search keywords, understand existing implementations. | Read-only; write and state-changing tools disabled; thoroughness can be specified per call (fast / medium / very thorough). |
| Plan | Read-only solution design: lay out the implementation path, key files, dependency order, and architecture trade-offs. | Read-only; outputs a step-by-step implementation plan listing the key files. |
| memory-manager | Manage cross-session memory, preferences, and facts; maintain personal and project instruction files. | Available only when memory management is enabled; reads and writes memory files only. |
| statusline-setup | Configure a custom status line: read shell config, generate scripts, update settings. | Interactive interface only. |
| qoder-guide | Answer questions about using and configuring Qoder CLI CN, Skills, Subagents, MCP, and Hooks. | Answers primarily based on official docs; interactive interface only. |
qodercn agents command. For each built-in Subagent's tool set, model, and invocation, see Built-in Agents and Skills.
Built-in Skills
Skills package common workflows into reusable capabilities. Built-in Skills ship with Qoder CLI CN and can be invoked directly as slash commands (for example /simplify); some are also triggered automatically by the model in suitable scenarios.
| Skill | Purpose |
|---|---|
/simplify | Review changed code for reusability, quality, and efficiency issues, launching multiple review perspectives in parallel and then fixing the findings. |
/debug | Enable debug logging for the current session, read the tail of the log, and help diagnose problems. |
/security-scan | Run a Qoder cloud security scan over the whole repository or a given path, supporting L2 lightweight and L3 deep review. |
/quest | Smart workflow orchestrator that guides you through feature development step by step with dedicated subagents. |
/mcp-config | Interactively add, update, or remove MCP server configuration. |
/loop | Run a prompt or slash command repeatedly at a fixed interval. |
/run | Launch and drive the project's actual application to observe changes at runtime. |
/verify | Verify that code changes meet expectations by running the application and observing its behavior. |
/remember | Review auto-memory entries, suggest promotions into instruction files, and identify stale, conflicting, and duplicate entries. |
/batch | Apply bulk changes across many files by spawning parallel worker agents in isolated git worktrees. |
/run-skill-generator | Generate a project-level Skill for the project's run and debug steps. |
How they trigger
Built-in Skills trigger in two ways:
- Manual invocation: type the corresponding slash command in the interactive interface (such as
/security-scan). - Automatic triggering: some Skills are used automatically when the model judges it appropriate; Skills marked as non-auto-triggering, such as
/debug,/security-scan, and/batch, run only when you invoke them explicitly.
Conditional availability
A few built-in Skills depend on specific prerequisites:
/batchrequires worktree isolation to be enabled (and the current directory to be a git repository)./rememberrequires auto-memory to be enabled.
qodercn skills command.
Workflows
Workflows orchestrate a series of steps into a repeatable process, ideal for solidifying multi-step tasks that recur within a team. Use /workflows to manage workflows, and /tasks and /kanban to track task progress. For detailed usage, see Workflows.
How to choose
- Need a one-off management or auxiliary operation within the session → use a slash command.
- Need to hand a class of tasks requiring its own context and standards to a focused executor → use a Subagent.
- Need to reuse a mature workflow (review, debugging, security review, looped execution, etc.) → use Skills.
- Need to solidify a multi-step task into a repeatable process → use a workflow.
Next steps
- Look up command details: Slash Commands, Built-in Agents and Skills.
- Extend capabilities: Built-in Agents and Skills Reference, Plugins.
- Bring in team knowledge: Knowledge Base.